Comparison Overview
Molecular Devices
Molecular Devices
3860 North First St, San Jose, CA, 95134, US
Last Update: 23/02/2026
Molecular Devices is one of the world’s leading providers of high-performance life science technology. We make advanced scientific discovery possible for academia, pharma, and biotech customers with platforms for high-throughput screening, genomic and cellular analysis,...
Gilead Sciences
333 Lakeside Drive, Foster City, 94404, US
Last Update: 14/09/2026
At Gilead, we set – and achieve – bold ambitions to create a healthier world for all people. From our pioneering virology medicines to our growing impact in oncology, we're delivering innovations once thought impossible in medicine. Our focus goes beyond medicines, and ...
Compliance Ranges Comparison
Molecular Devices
Gilead Sciences
Benchmark & Cyber Underwriting Signals
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Molecular Devices in 2026.
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Gilead Sciences in 2026.
Incident History - Molecular Devices (X = Date, Y = Severity)
Molecular Devices cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Gilead Sciences (X = Date, Y = Severity)
Gilead Sciences cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Molecular Devices
Gilead Sciences
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.