Comparison Overview
Expeditors Recruiting
Expeditors Recruiting
1200 3rd Ave, Seattle, 98104, US
Last Update: 31/12/2025
Welcome to Expeditors' Recruiting, your gateway to a world of exciting career possibilities. We are a leading global logistics company renowned for our commitment to excellence, innovation, and customer satisfaction. At Expeditors, we believe that our success is driven ...
NFI
2 Cooper St, Camden, 08102, US
Last Update: 08/09/2026
NFI is a fully integrated North American supply chain solutions provider headquartered in Camden, New Jersey. Privately held by the Brown family since 1932, we generate over $3.8 billion annually and employ 17,000+ associates. Guided by our values of family, integrity, ...
Compliance Ranges Comparison
Expeditors Recruiting
NFI
Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for Expeditors Recruiting in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for NFI in 2026.
Incident History - Expeditors Recruiting (X = Date, Y = Severity)
Expeditors Recruiting cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NFI (X = Date, Y = Severity)
NFI cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Expeditors Recruiting
NFI
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.