Comparison Overview
Hologic, Inc.
Hologic, Inc.
250 Campus Drive, Marlborough, 01752, US
Last Update: 31/03/2026
We’re an innovative medical technology company whose purpose is to enable healthier lives everywhere, every day. While we discover and develop groundbreaking products and services that benefit everyone, we are especially passionate about those that advance women’s healt...
Alcon
Avenue Louis-Casaï 58, Geneva, 1216, CH
Last Update: 13/09/2026
Alcon helps people see brilliantly. As the global leader in eye care with a heritage spanning over 75 years, we offer the broadest portfolio of products to enhance sight and improve people’s lives. Our Surgical and Vision Care products touch the lives of more than 260 m...
Compliance Ranges Comparison
Hologic, Inc.
Alcon
Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Hologic, Inc. in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
Alcon has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Hologic, Inc. (X = Date, Y = Severity)
Hologic, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Alcon (X = Date, Y = Severity)
Alcon cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hologic, Inc.
Alcon
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.