Comparison Overview
Novocure
Novocure
Neuhofstrasse 21, Baar, 6340, CH
Last Update: 01/09/2026
Novocure is a global oncology company working to extend survival in some of the most aggressive forms of cancer through the development and commercialization of its innovative therapy, Tumor Treating Fields. Novocure’s commercialized products are approved in certain co...
Beckman Coulter Diagnostics
250 S Kraemer Blvd, Brea, California, US, 92821
Last Update: 13/09/2026
A global leader in advanced diagnostics, Beckman Coulter has challenged convention to elevate the diagnostic laboratory’s role in improving patient health for more than 80 years. Our mission is to Relentlessly Reimagine Healthcare, One Diagnosis at a Time – and we do th...
Compliance Ranges Comparison
Novocure
Beckman Coulter Diagnostics
Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
Novocure has 8.26% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Beckman Coulter Diagnostics in 2026.
Incident History - Novocure (X = Date, Y = Severity)
Novocure cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Beckman Coulter Diagnostics (X = Date, Y = Severity)
Beckman Coulter Diagnostics cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Novocure
Beckman Coulter Diagnostics
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.