Comparison Overview
Pactiv Evergreen Inc.
Pactiv Evergreen Inc.
1900 W. Field Court, Lake Forest, IL, 60045, US
Last Update: 25/02/2026
Pactiv Evergreen is one of the largest manufacturers of fresh food & beverage packaging in North America, with market leading positions across a broad range of products. Through the collaborative efforts of our 14,000+ employees, we bring our Purpose of Packaging a Bet...
Tetra Pak
70 Avenue Général-Guisan, CH-1009 PULLY/LAUSANNE, Case Postale 446, CH
Last Update: 14/09/2026
We’re here to make food safe and available. It’s why we provide advanced food production systems, from product creation and recipe testing to processing, filling, packaging, logistics, services and beyond. We support almost every food and beverage category with tailored...
Compliance Ranges Comparison
Pactiv Evergreen Inc.
Tetra Pak
Benchmark & Cyber Underwriting Signals
Incidents vs Packaging and Containers Manufacturing Industry Avg (This Year)
No incidents recorded for Pactiv Evergreen Inc. in 2026.
Incidents vs Packaging and Containers Manufacturing Industry Avg (This Year)
No incidents recorded for Tetra Pak in 2026.
Incident History - Pactiv Evergreen Inc. (X = Date, Y = Severity)
Pactiv Evergreen Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Tetra Pak (X = Date, Y = Severity)
Tetra Pak cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Pactiv Evergreen Inc.
Tetra Pak
FAQ
Latest Global CVEs
vLLM through 0.29.0 fails to properly clean up decode-side metadata for rejected inference requests in prefill/decode disaggregated deployments. Remote attackers can submit requests with max_tokens=0 to exhaust decode-worker memory without bound until the worker restarts.
- https://github.com/vllm-project/vllm
- https://github.com/vllm-project/vllm/blob/v0.29.0/vllm/distributed/kv_transfer/kv_connector/v1/nixl/push_worker.py#L162-L181
- https://github.com/vllm-project/vllm/pull/55677
- https://www.vulncheck.com/advisories/vllm-through-0.29.0-memory-exhaustion-via-rejected-requests
redis-parser through 3.0.0 contains a denial of service vulnerability in the RESP protocol parser that allows malicious Redis endpoints to crash the client process through unbounded recursion on nested arrays. Attackers can send crafted RESP byte streams with repeated array headers that exhaust the V8 call stack, causing an uncaught RangeError that terminates the Node.js process without triggering error handling callbacks.
- https://github.com/NodeRedis/node-redis-parser
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L204-L213
- https://github.com/NodeRedis/node-redis-parser/blob/701655430f5f7d9ca00892a02f7eefcbc1193a98/lib/parser.js#L291-L306
- https://github.com/redis/ioredis/issues/2108
- https://www.vulncheck.com/advisories/redis-parser-through-3.0.0-denial-of-service-via-unbounded-recursion
Improper neutralization of special elements in output used by a downstream component ('injection') in Azure Cosmos DB allows an authorized attacker to elevate privileges over a network.
Server-side request forgery (ssrf) in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.
Missing authentication for critical function in Azure AI Foundry allows an unauthorized attacker to elevate privileges over a network.