Comparison Overview
UPS
UPS
55 Glenlake Parkway, NE, Atlanta, 30328, US
Last Update: 15/09/2026
Operating in more than 200 countries and territories, we’re committed to moving our world forward by delivering what matters. Beginning as a small messenger service, UPS was started by two enterprising teenagers and a $100 loan. Now, we’re almost 500,000 UPSers strong, ...
STEF
93 Boulevard Malesherbes, Paris, 75008, FR
Last Update: 14/09/2026
STEF group is the European leader for temperature controlled logistics and transport. Our 22,000 employees in 8 countries are dedicated to serve everyday agrifood, distribution, foodservice and seafood players with the highest standards of security, rapidity and quality...
Compliance Ranges Comparison
UPS
STEF
Benchmark & Cyber Underwriting Signals
Incidents vs Truck Transportation Industry Avg (This Year)
UPS has 47.37% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Truck Transportation Industry Avg (This Year)
No incidents recorded for STEF in 2026.
Incident History - UPS (X = Date, Y = Severity)
UPS cyber incidents detection timeline including parent company and subsidiaries.
Incident History - STEF (X = Date, Y = Severity)
STEF cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
UPS
STEF
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.