Comparison Overview
Baxter Healthcare India

Baxter Healthcare India
5th floor, IN-GUR-TWB, Building No.9, DLF Cyber City, DLF Phase 3, Sector 24, Gurugram, 122002, IN
Last Update: 22/01/2026
Every day, millions of patients, caregivers and providers around the world rely on Baxter’s leading portfolio of diagnostic, critical care, nutrition, kidney care, hospital and surgical products and solutions. For 90 years, we’ve been making an impact at the critical in...

Stryker
2825 Airview Boulevard, Kalamazoo, 49002, US
Last Update: 13/07/2026
Stryker is a global leader in medical technologies and, together with our customers, we are driven to make healthcare better. We offer innovative products and services in MedSurg, Neurotechnology and Orthopaedics that help improve patient and healthcare outcomes. Alongs...
Compliance Ranges Comparison

Baxter Healthcare India







Stryker






Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Baxter Healthcare India in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
Stryker has 1356.31% more incidents than the average of all companies with at least one recorded incident.
Incident History - Baxter Healthcare India (X = Date, Y = Severity)
Baxter Healthcare India cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Stryker (X = Date, Y = Severity)
Stryker cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Baxter Healthcare India

Stryker
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.