Comparison Overview
Scania Tanzania
Scania Tanzania
Nyerere Road, Dar es Salaam, +255, TZ
Last Update: 12/04/2026
Scania deals with heavy truck, buses and Industrial Gensets. Scania has long history in Tanzania back in 1973, owned by Scania CV AB reporting to Scania East Africa based in Kenya since 2015. We serve transporters and support them with workshop and parts across the cou...
Schneider
3101 S. Packerland Drive, Green Bay, WI, US, 54306-2545
Last Update: 13/09/2026
Put us on the job and consider it done. Schneider is a premier provider of transportation and logistics services headquartered in Green Bay, Wisconsin, and with offices in Chicago, Dallas and many cities in between. Offering one of the broadest portfolios in the industr...
Compliance Ranges Comparison
Scania Tanzania
Schneider
Benchmark & Cyber Underwriting Signals
Incidents vs Truck Transportation Industry Avg (This Year)
No incidents recorded for Scania Tanzania in 2026.
Incidents vs Truck Transportation Industry Avg (This Year)
No incidents recorded for Schneider in 2026.
Incident History - Scania Tanzania (X = Date, Y = Severity)
Scania Tanzania cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Schneider (X = Date, Y = Severity)
Schneider cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Scania Tanzania
Schneider
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.