Comparison Overview
Munich Re Specialty - North America

Munich Re Specialty - North America
555 College Rd E, P.O. Box 5241, Princeton, New Jersey, US, 08540
Last Update: 20/01/2026
Munich Re Specialty combines premier specialty expertise, capabilities, and products to offer partners and customers simplified access to a wide range of specialty insurance solutions and services. With Munich Re’s renowned stability, robust financial backing, and dedic...

Aviva
80 Fenchurch Street, London, EC3M 4AE, , GB
Last Update: 02/04/2026
💛 We're a leading Insurance, Wealth & Retirement business. 📣 Follow for #LifeAtAviva. Aviva is nothing without our people. Living up to our purpose to be with you today for a better tomorrow applies to those we work with just as much as it does to our custom...
Compliance Ranges Comparison

Munich Re Specialty - North America







Aviva






Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Munich Re Specialty - North America in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Aviva in 2026.
Incident History - Munich Re Specialty - North America (X = Date, Y = Severity)
Munich Re Specialty - North America cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Aviva (X = Date, Y = Severity)
Aviva cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Munich Re Specialty - North America

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