Comparison Overview
Medibank

Medibank
720 Bourke Street Docklands, Melbourne, Victoria, AU, 3008
Last Update: 24/09/2026
At Medibank, we are motivated by improving the health and wellbeing of all Australians. We’re passionate about building a better health system that’s centred on people and sustainable for the long term. That commitment extends to our people, too. In 2026, we were reco...

FWD Insurance
13/F, City Plaza 3, 14 Taikoo Wan Road, Quarry Bay, _, HK
Last Update: 07/09/2026
FWD Group (1828.HK) is a pan-Asian life and health insurance business that serves approximately 34 million customers across 10 markets, including BRI Life in Indonesia. FWD’s customer-led and tech-enabled approach aims to deliver innovative propositions, easy-to-underst...
Compliance Ranges Comparison

Medibank







FWD Insurance






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

Medibank

FWD Insurance
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.