Comparison Overview
Pilot Freight Services
Pilot Freight Services
2 Braxton Way, Glen Mills, 19342, US
Last Update: 06/03/2026
Pilot - A Maersk Company is a full-service global transportation and logistics provider with over 75 locations throughout North America, western European operations, and administration offices in the Netherlands and Spain. Our freight forwarding services encompass every...
Yellow
501 Commerce St. Suite, 1120, Nashville, 37203, US
Last Update: 13/09/2026
Yellow, a Fortune 500 company headquartered in Nashville, TN is one of the largest super-regional less-than-truckload (LTL) companies in North America. Nearly 100 years ago, Yellow created the LTL industry, and now it comprises four successful regional LTL companies and...
Compliance Ranges Comparison
Pilot Freight Services
Yellow
Benchmark & Cyber Underwriting Signals
Incidents vs Truck Transportation Industry Avg (This Year)
No incidents recorded for Pilot Freight Services in 2026.
Incidents vs Truck Transportation Industry Avg (This Year)
No incidents recorded for Yellow in 2026.
Incident History - Pilot Freight Services (X = Date, Y = Severity)
Pilot Freight Services cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Yellow (X = Date, Y = Severity)
Yellow cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Pilot Freight Services
Yellow
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.