Comparison Overview
Danaher Life Sciences
Danaher Life Sciences
500 Old Connecticut Path, Framingham, 01701, US
Last Update: 29/11/2025
The Life Sciences companies of Danaher integrate the deep scientific expertise of our individual operating companies with the robust engineering know-how of the Danaher Business System to create innovative workflows that significantly bend the drug development time curv...
Roche
Grenzacherstrasse, Switzerland 🇨🇭 , 4070, CH
Last Update: 17/09/2026
Roche is a global pioneer in pharmaceuticals and diagnostics focused on advancing science to improve people’s lives. The combined strengths of pharmaceuticals and diagnostics under one roof have made Roche the leader in personalised healthcare – a strategy that aims to ...
Compliance Ranges Comparison
Danaher Life Sciences
Roche
Benchmark & Cyber Underwriting Signals
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Danaher Life Sciences in 2026.
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Roche in 2026.
Incident History - Danaher Life Sciences (X = Date, Y = Severity)
Danaher Life Sciences cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Roche (X = Date, Y = Severity)
Roche cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Danaher Life Sciences
Roche
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.