Comparison Overview
Axalta ANZ – Australia & New Zealand

Axalta ANZ – Australia & New Zealand
16 DARLING STREET, MARSDEN PARK, 2765, AU
Last Update: 03/02/2026
At Axalta, we continuously innovate to help protect, improve, and advance everything we see and touch. Across our businesses — refinish, mobility, and industrial — we use technologies and processes to develop innovative products that help accelerate our customers’ busin...

LyondellBasell
LyondellBasell Tower, Ste. 700, 1221 McKinney Street, Houston, TX, US, 77010
Last Update: 07/10/2026
We are LyondellBasell (NYSE: LYB) – a leader in the global chemical industry creating solutions for everyday sustainable living. Through advanced technology and focused investments, we are enabling a circular and low carbon economy. Across all we do, we aim to unlock va...
Compliance Ranges Comparison

Axalta ANZ – Australia & New Zealand







LyondellBasell






Benchmark & Cyber Underwriting Signals
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for Axalta ANZ – Australia & New Zealand in 2026.
Incidents vs Chemical Manufacturing Industry Avg (This Year)
No incidents recorded for LyondellBasell in 2026.
Incident History - Axalta ANZ – Australia & New Zealand (X = Date, Y = Severity)
Axalta ANZ – Australia & New Zealand cyber incidents detection timeline including parent company and subsidiaries.
Incident History - LyondellBasell (X = Date, Y = Severity)
LyondellBasell cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Axalta ANZ – Australia & New Zealand

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