Comparison Overview
Smit Lamnalco

Smit Lamnalco
Waalhaven O.Z. 85, Rotterdam, Nederland, 3087 BM, NL
Last Update: 20/01/2026
Smit Lamnalco provides first class, reliable and customised marine support in any environment. We ensure safe and efficient operations in any part of the world. Our quality is in our people. With their dedication, we go to extremes to deliver the best towage and relate...

Hapag-Lloyd AG
Ballindamm 25, Hamburg, 20095, DE
Last Update: 11/09/2026
With a fleet of 302 modern container ships and a total transport capacity of 2.5 million TEU, Hapag-Lloyd is one of the world’s leading liner shipping companies. In the Liner Shipping segment, the Company has 15,200 employees and 400 offices in 140 countries. Hapag-Lloy...
Compliance Ranges Comparison

Smit Lamnalco







Hapag-Lloyd AG






Benchmark & Cyber Underwriting Signals
Incidents vs Maritime Transportation Industry Avg (This Year)
No incidents recorded for Smit Lamnalco in 2026.
Incidents vs Maritime Transportation Industry Avg (This Year)
Hapag-Lloyd AG has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Smit Lamnalco (X = Date, Y = Severity)
Smit Lamnalco cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hapag-Lloyd AG (X = Date, Y = Severity)
Hapag-Lloyd AG cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Smit Lamnalco

Hapag-Lloyd AG
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.