Comparison Overview
Tandem Diabetes Care

Tandem Diabetes Care
12400 High Bluff Drive , None, San Diego, California, US, 92130
Last Update: 02/04/2026
Tandem Diabetes Care, a global insulin delivery and diabetes technology company, manufactures and sells advanced automated insulin delivery systems that reduce the burden of diabetes management, while creating new possibilities for patients, their loved ones, and health...

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

Tandem Diabetes Care







Zimmer Biomet






Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Tandem Diabetes Care in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Zimmer Biomet in 2026.
Incident History - Tandem Diabetes Care (X = Date, Y = Severity)
Tandem Diabetes Care 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

Tandem Diabetes Care

Zimmer Biomet
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout