Comparison Overview
Victory Power Solutions

Victory Power Solutions
Addison, 75001, US
Last Update: 19/02/2026
Making complex markets simple by providing straight forward solutions to an ever-changing energy procurement challenge. We empower commercial energy consumers to focus on profits while Victory delivers valuable energy procurement strategies and solutions. As an indepen...

Oxy
Houston, 77046, US
Last Update: 01/04/2026
Oxy is an international energy company with assets primarily in the United States, the Middle East and North Africa. We are one of the largest oil producers in the U.S., including a leading producer in the Permian and DJ basins, and offshore Gulf of Mexico. Our midstrea...
Compliance Ranges Comparison

Victory Power Solutions







Oxy






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

Victory Power Solutions

Oxy
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.