Comparison Overview
ComEd

ComEd
ComEd, Chicago, IL, 60726, US
Last Update: 12/03/2026
At ComEd, we believe in being an energy partner, not just an energy provider. Being a provider means we deliver electricity to over 4 million customers across northern Illinois, which accounts for about 70 percent of the state’s population. We do so safely and reliabl...

Dubai Electricity & Water Authority - DEWA
Sheikh Rashid Road, Umm Hureir2, Umm Hureir, Dubai. Makani Number: 31079 91073, Dubai, Dubai, AE, 564
Last Update: 01/04/2026
Dubai Electricity and Water Authority (DEWA), established on 1 January 1992, stands at the forefront of sustainable energy and water management. With a dedicated workforce of over 11,000 employees, we ensure reliable services across the entire chain of electricity and w...
Compliance Ranges Comparison

ComEd







Dubai Electricity & Water Authority - DEWA






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

ComEd

Dubai Electricity & Water Authority - DEWA
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.