Comparison Overview
Krones Recycling
Krones Recycling
Böhmerwaldstraße 5, Neutraubling, 93073, DE
Last Update: 27/01/2026
The Krones Group, headquartered in Neutraubling, Germany, plans, develops, and manufactures machines and complete lines for the fields of process technology, bottling, canning and packaging, plus intralogistics and recycling. Speaking of recycling: From a consumer's vi...
Voith Group
Sankt-Poltener-Strasse 43, Heidenheim an der Brenz, 89522, DE
Last Update: 14/09/2026
The Voith Group is a global technology company. With its broad portfolio of systems, products, services and digital applications, Voith sets standards in the markets of energy, paper, raw materials and transport. Founded in 1867, Voith today has around 22,000 employees,...
Compliance Ranges Comparison
Krones Recycling
Voith Group
Benchmark & Cyber Underwriting Signals
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Krones Recycling in 2026.
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Voith Group in 2026.
Incident History - Krones Recycling (X = Date, Y = Severity)
Krones Recycling cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Voith Group (X = Date, Y = Severity)
Voith Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Krones Recycling
Voith Group
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.