Comparison Overview
Wyda

Wyda
Alameda Wyda 109, Sorocaba, São Paulo, 18086-600, BR
Last Update: 09/03/2026
Desde 1992, a Wyda oferece, além de uma linha completa de embalagens descartáveis para alimentos, a garantia de um produto higiênico e confiável, unindo praticidade, qualidade e sustentabilidade. Com um portfólio com mais de 200 produtos, somos a primeira empresa de em...

Sonoco
1 North Second Street, Hartsville, 29550, US
Last Update: 14/09/2026
Founded in 1899, Sonoco (NYSE: SON) is a global leader in value-added, sustainable metal and paper consumer and industrial packaging. The Company had net sales of $7.5 billion from continuing operations in 2025 and has approximately 22,000 employees working in 265 opera...
Compliance Ranges Comparison

Wyda







Sonoco






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

Wyda

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