Comparison Overview
Gamida Cell Ltd.
Gamida Cell Ltd.
673 Boylston St, Boston, 02116, US
Last Update: 01/03/2026
Gamida Cell is a cell therapy pioneer working to turn cells into powerful therapeutics. Our proprietary nicotinamide (NAM) technology expands the number of cells while maintaining their intrinsic properties to create potentially curative cell therapy products and candid...
Genentech
1 Dna Way, South San Francisco, California, US, 94080
Last Update: 11/09/2026
About Genentech We're passionate about finding solutions for people facing the world's most difficult-to-treat conditions. That is why we use cutting-edge science to create and deliver innovative medicines around the globe. To us, science is personal. Making a differe...
Compliance Ranges Comparison
Gamida Cell Ltd.
Genentech
Benchmark & Cyber Underwriting Signals
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Gamida Cell Ltd. in 2026.
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for Genentech in 2026.
Incident History - Gamida Cell Ltd. (X = Date, Y = Severity)
Gamida Cell Ltd. cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Genentech (X = Date, Y = Severity)
Genentech cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Gamida Cell Ltd.
Genentech
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.