Comparison Overview
Zimmer Biomet EMEA
Zimmer Biomet EMEA
Zug, Switzerland, 6300, CH
Last Update: 10/03/2026
Zimmer Biomet is a global medical technology leader with a comprehensive portfolio designed to maximize mobility. Our EMEA headquarters are in Zug, Switzerland. Our global team designs, manufactures and markets effective, innovative solutions that support orthopaedic s...
Henry Schein
135 Duryea Road, Melville, 11747, US
Last Update: 09/09/2026
Henry Schein, Inc. (Nasdaq: HSIC) is a products, services, and technology platforms company for healthcare customers. With more than 25,000 Team Schein Members worldwide, the Company's network of trusted advisors provides more than 1 million customers globally with more...
Compliance Ranges Comparison
Zimmer Biomet EMEA
Henry Schein
Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Zimmer Biomet EMEA in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
Henry Schein has 2.91% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Zimmer Biomet EMEA (X = Date, Y = Severity)
Zimmer Biomet EMEA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Henry Schein (X = Date, Y = Severity)
Henry Schein cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Zimmer Biomet EMEA
Henry Schein
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.