Comparison Overview
Jungheinrich Belgium

Jungheinrich Belgium
Esperantolaan 1, Leuven (Heverlee), Vlaams-Brabant 3001, BE
Last Update: 08/05/2026
With more than 60 years of experience, Jungheinrich is one of the world’s leading intralogistics specialists. Jungheinrich employs more than 18,000 employees worldwide, all tasked with developing, implementing, optimising and maintaining high-quality intralogistics solu...

Sulzer
Neuwiesenstrasse 15, Winterthur, 8401, CH
Last Update: 24/09/2026
Sulzer is a global leader in critical applications for core infrastructure and processes for large essential industries around the world. We ensure the security, quality and durability of critical goods and services by supporting energy security, natural resource manage...
Compliance Ranges Comparison

Jungheinrich Belgium







Sulzer






Benchmark & Cyber Underwriting Signals
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Jungheinrich Belgium in 2026.
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Sulzer in 2026.
Incident History - Jungheinrich Belgium (X = Date, Y = Severity)
Jungheinrich Belgium cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sulzer (X = Date, Y = Severity)
Sulzer cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Jungheinrich Belgium

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