Comparison Overview
Sealed Air Corporation

Sealed Air Corporation
2415 Cascade Pointe Boulevard, Charlotte, NC, US, 28208
Last Update: 12/09/2026
Sealed Air is in business to protect, to solve critical packaging challenges, and to make our world better than we find it. Our automated packaging solutions promote a safer, more resilient, and less wasteful global food, fluids and liquids supply chain, enable e-commer...

Amcor
Thurgauerstrasse 34, Zurich, CH, CH-8050
Last Update: 13/09/2026
As a global leader in packaging solutions for consumer and healthcare products, our industry-leading innovation capabilities, global scale and technical expertise help our customers grow and meet the needs of millions of consumers every day. We accelerate the possible b...
Compliance Ranges Comparison

Sealed Air Corporation







Amcor






Benchmark & Cyber Underwriting Signals
Incidents vs Packaging and Containers Manufacturing Industry Avg (This Year)
No incidents recorded for Sealed Air Corporation in 2026.
Incidents vs Packaging and Containers Manufacturing Industry Avg (This Year)
No incidents recorded for Amcor in 2026.
Incident History - Sealed Air Corporation (X = Date, Y = Severity)
Sealed Air Corporation cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amcor (X = Date, Y = Severity)
Amcor cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sealed Air Corporation

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