Comparison Overview
BioKryo
BioKryo
8, Avenue Gutenberg, Marne-la-Vallée, Île-de-France, 77600, FR
Last Update: 01/03/2026
BioKryo, Business Unit of Air Liquide Healthcare, offers tailor-made storage solutions to all structures confronted with a need in the management or the storage of biological samples. Member of European Business Unit Biobanking, BioKryo is a Biological Resource Cente...
Amgen
One Amgen Center Drive, Thousand Oaks, 91320, US
Last Update: 11/09/2026
Amgen harnesses the best of biology and technology to fight the world’s toughest diseases, and make people’s lives easier, fuller and longer. We helped establish the biotechnology industry, and we remain on the cutting-edge of innovation, using technology and human gene...
Compliance Ranges Comparison
BioKryo
Amgen
Benchmark & Cyber Underwriting Signals
Incidents vs Biotechnology Research Industry Avg (This Year)
No incidents recorded for BioKryo in 2026.
Incidents vs Biotechnology Research Industry Avg (This Year)
Amgen has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - BioKryo (X = Date, Y = Severity)
BioKryo cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Amgen (X = Date, Y = Severity)
Amgen cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BioKryo
Amgen
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.