Comparison Overview
SJL
SJL
SJL (San José Lopez), Tanger, MA
Last Update: 25/03/2026
As a leader in international transport and logistics on the Europe-Africa corridor, SJL helps its customers optimize their supply chain. We offer integrated, customized and multimodal solutions for the entire transport and logistics chain, combining international frei...
Yusen Logistics
Shinagawa Seaside Park Tower 4-12-4 Higashishinagawa, Shinagawa-ku, Tokyo, JP, 1400002
Last Update: 13/09/2026
Yusen Logistics is the insight-driven, customer-centric logistics partner to global business. We deliver this through an extended range of services from International Freight Forwarding and Contract Logistics to Supply Chain Solutions and Industry insights covering the ...
Compliance Ranges Comparison
SJL
Yusen Logistics
Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for SJL in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for Yusen Logistics in 2026.
Incident History - SJL (X = Date, Y = Severity)
SJL cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Yusen Logistics (X = Date, Y = Severity)
Yusen Logistics cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
SJL
Yusen 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.