Comparison Overview
INEOS Tyssedal

INEOS Tyssedal
Naustbakken 1, Tyssedal, N-5770, NO
Last Update: 22/12/2025
INEOS Tyssedal ilmenite upgrading facility has a long and stable production history, having commenced operations in 1986. It is one of only six such operating facilities of its type in the world and the only one in Europe. INEOS Tyssedal is part of INEOS. ETI upgrades ...

Norsk Hydro
Drammensveien 264, Oslo, 0283, NO
Last Update: 20/09/2026
Hydro is a leading industrial company that builds businesses and partnerships for a more sustainable future. We develop industries that matter to people and society. Since 1905, Hydro has turned natural resources into valuable products for people and businesses, creati...
Compliance Ranges Comparison

INEOS Tyssedal







Norsk Hydro






Benchmark & Cyber Underwriting Signals
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for INEOS Tyssedal in 2026.
Incidents vs Mining Industry Avg (This Year)
No incidents recorded for Norsk Hydro in 2026.
Incident History - INEOS Tyssedal (X = Date, Y = Severity)
INEOS Tyssedal cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Norsk Hydro (X = Date, Y = Severity)
Norsk Hydro cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

INEOS Tyssedal

Norsk Hydro
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.