Comparison Overview
EY

EY
6 More London Place, London, SE1 2DA, GB
Last Update: 29/07/2026
EY is building a better working world by creating new value for clients, people, society, the planet, while building trust in the capital markets. Enabled by data, AI and advanced technology, EY teams help clients shape the future with confidence and develop answers fo...

Mercer
New York, New York, New York, 10036, US
Last Update: 19/05/2026
At Mercer, A Marsh business, we’re helping our clients realize their investment objectives, shape the future of work, and enhance health and retirement outcomes for their people. As a business of Marsh, for 80 years, we’ve been helping our clients, colleagues and comm...
Compliance Ranges Comparison

EY







Mercer






Benchmark & Cyber Underwriting Signals
Incidents vs Professional Services Industry Avg (This Year)
EY has 100.0% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Professional Services Industry Avg (This Year)
No incidents recorded for Mercer in 2026.
Incident History - EY (X = Date, Y = Severity)
EY cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mercer (X = Date, Y = Severity)
Mercer cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

EY

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