Comparison Overview
Dürr

Dürr
Carl-Benz-Straße 34, Bietigheim-Bissingen, Baden-Württemberg, 74321, DE
Last Update: 30/11/2025
Dürr Systems AG is part of the Dürr Group, one of the worldwide leading machinery and plant manufacturers with distinctive expertise in the fields of automation, digitalization and energy efficiency. Dürr Systems AG comprises three of the Dürr Group's five business unit...

ZEISS Group
Carl-Zeiss-Str. 22, Oberkochen, 73447, DE
Last Update: 13/09/2026
ZEISS is an internationally leading technology enterprise operating in the fields of optics and optoelectronics. In the previous fiscal year, the ZEISS Group generated annual revenue totaling almost 12 billion euros in its four segments Semiconductor Manufacturing Techn...
Compliance Ranges Comparison

Dürr







ZEISS Group






Benchmark & Cyber Underwriting Signals
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for Dürr in 2026.
Incidents vs Machinery Manufacturing Industry Avg (This Year)
No incidents recorded for ZEISS Group in 2026.
Incident History - Dürr (X = Date, Y = Severity)
Dürr cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ZEISS Group (X = Date, Y = Severity)
ZEISS Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Dürr

ZEISS 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.