Comparison Overview
UPS Healthcare
UPS Healthcare
12380 Morris Rd, Alpharetta, 30005, US
Last Update: 06/01/2026
Join the revolution in healthcare logistics with UPS Healthcare. With an unwavering commitment to innovation and improvement, our team of 10,000 experts is transforming the industry as we know it. We prioritize quality and put patients first, and we offer a range of bes...
CEVA Logistics
10, Place de la Joliette, Marseille, 13002, FR
Last Update: 13/09/2026
CEVA provides world-class supply chain solutions for large and medium-size national and multinational companies across the globe. As an industry leader, CEVA offers customers complete supply chain design and implementation in contract logistics and freight management, a...
Compliance Ranges Comparison
UPS Healthcare
CEVA Logistics
Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for UPS Healthcare in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
CEVA Logistics has 385.44% more incidents than the average of all companies with at least one recorded incident.
Incident History - UPS Healthcare (X = Date, Y = Severity)
UPS Healthcare cyber incidents detection timeline including parent company and subsidiaries.
Incident History - CEVA Logistics (X = Date, Y = Severity)
CEVA Logistics cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
UPS Healthcare
CEVA Logistics
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.