Comparison Overview
PacifiCorp

PacifiCorp
825 NE Multnomah Street, Portland, Oregon, US, 97232
Last Update: 02/04/2026
As a locally managed, wholly owned subsidiary of Berkshire Hathaway Energy Company, PacifiCorp is a leading western U.S. energy services provider and the largest grid owner/operator in the West. Serving 2 million customers across 143,000 square miles in six western stat...

RWE
RWE Platz 1, Essen, 45141, DE
Last Update: 02/04/2026
RWE is leading the way to a clean energy world. With its investment and growth strategy Growing Green, RWE is contributing significantly to the success of the energy transition and the decarbonisation of the energy system. Around 20,000 employees work for the company in...
Compliance Ranges Comparison

PacifiCorp







RWE






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

PacifiCorp

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