Comparison Overview
Greatbatch Medical
Greatbatch Medical
2595 North Dallas Pkwy, Frisco, 75034, US
Last Update: 01/03/2026
Head over to our new page for Integer: https://www.linkedin.com/company/integer-holdings/ Integer Holdings Corporation (NYSE:ITGR) is the largest medical device outsource (MDO) manufacturer in the world serving the cardiac, neuromodulation, orthopedics, vascular, advan...
Zimmer Biomet
345 East Main Street, Warsaw, 46580, US
Last Update: 13/09/2026
Zimmer Biomet is a global medical technology leader with a comprehensive portfolio designed to maximize mobility and improve health. We advance our mission to alleviate pain and improve the quality of life for patients around the world with our innovative products and s...
Compliance Ranges Comparison
Greatbatch Medical
Zimmer Biomet
Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Greatbatch Medical in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Zimmer Biomet in 2026.
Incident History - Greatbatch Medical (X = Date, Y = Severity)
Greatbatch Medical cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Zimmer Biomet (X = Date, Y = Severity)
Zimmer Biomet cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Greatbatch Medical
Zimmer Biomet
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.