Comparison Overview
Volcano Corporation

Volcano Corporation
3721 Valley Centre Drive Suite 500, San Diego, CA, 92130, US
Last Update: 28/02/2026
Through its multi-modality platform, Volcano Corporation is the global leader in intravascular imaging for coronary and peripheral applications, and physiology. The company also offers a suite of peripheral therapeutic devices. The company's broad range of technologies ...

Zimmer Biomet
345 East Main Street, P.O. Box 708, Warsaw, Indiana, US, 46580
Last Update: 01/04/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

Volcano Corporation







Zimmer Biomet






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

Volcano Corporation

Zimmer Biomet
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.