Comparison Overview
thyssenkrupp
thyssenkrupp
thyssenkrupp Allee 1, Essen, 45143, DE
Last Update: 07/09/2026
thyssenkrupp is an international industrial and technology group with more than 93,000 employees. In the fiscal year 2024/2025, the company generated sales of around €33 billion in 48 countries. Its business activities are bundled in five segments: Automotive Technology...
Danfoss
Nordborgvej 81, Nordborg, DK, 6430
Last Update: 13/09/2026
Danfoss engineers solutions that increase machine productivity, reduce emissions, lower energy consumption, and enable electrification. Our solutions are used in such areas as refrigeration, air conditioning, heating, power conversion, motor control, industrial machine...
Compliance Ranges Comparison
thyssenkrupp
Danfoss
Benchmark & Cyber Underwriting Signals
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for thyssenkrupp in 2026.
Incidents vs Industrial Machinery Manufacturing Industry Avg (This Year)
Danfoss has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - thyssenkrupp (X = Date, Y = Severity)
thyssenkrupp cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Danfoss (X = Date, Y = Severity)
Danfoss cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
thyssenkrupp
Danfoss
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.