Comparison Overview
Swiss Re Corporate Solutions

Swiss Re Corporate Solutions
50/60 Mythenquai, None, Zurich, Zurich, CH, 8022
Last Update: 26/03/2026
Swiss Re Corporate Solutions provides a range of traditional and innovative commercial insurance products and risk-transfer solutions through a global team of commercial insurance experts. Learn more about Risk Data & Services at https://corporatesolutions.swissre.com/...

AXA XL
One Bermudiana Road, Hamilton, Bermuda, BM, HM08
Last Update: 01/04/2026
We are a leading provider of insurance and reinsurance offering innovative risk management solutions for businesses worldwide. We partner with those who move the world forward, navigating complex risks and working across diverse industries to support and empower our cli...
Compliance Ranges Comparison

Swiss Re Corporate Solutions







AXA XL






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

Swiss Re Corporate Solutions

AXA XL
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.