Comparison Overview
Subsea Production Systems

Subsea Production Systems
N/A
Last Update: 06/03/2026
Whether topside, subsea, or a hybrid combination is required for your field, our diverse process and production solutions cover the life of a development, from concept to greenfield and brownfield, optimizing existing facilities or extending field life. As experts in ...

YPF
Macacha Guemes 515, Capital Federal, ., AR
Last Update: 01/04/2026
Somos el mayor productor de Oil & Gas de la Argentina, con sólidos resultados y capacidad para llevar adelante los proyectos que convertirán al país en un exportador de energía a nivel mundial. Nuestro objetivo es convertirnos en una empresa no convencional de clase mu...
Compliance Ranges Comparison

Subsea Production Systems







YPF






Benchmark & Cyber Underwriting Signals
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for Subsea Production Systems in 2026.
Incidents vs Oil and Gas Industry Avg (This Year)
No incidents recorded for YPF in 2026.
Incident History - Subsea Production Systems (X = Date, Y = Severity)
Subsea Production Systems cyber incidents detection timeline including parent company and subsidiaries.
Incident History - YPF (X = Date, Y = Severity)
YPF cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Subsea Production Systems

YPF
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.