Comparison Overview
OrthoSensor, now part of Stryker

OrthoSensor, now part of Stryker
1855 Griffin Road, Dania, 33004, US
Last Update: 12/03/2026
As of January 5, 2021, OrthoSensor is now part of Stryker. With technologies spanning the continuum of care in total joint replacement, together, Stryker and OrthoSensor, Inc. will empower surgeons with intelligent devices and comprehensive data-driven solutions. This p...

Olympus Corporation
Nishi-shinjuku 2-3-1 Shinjuku Monolith, Shinjuku-ku, JP
Last Update: 01/04/2026
Olympus is passionate about creating customer-driven solutions for the medical industry. For more than 100 years, Olympus has focused on making people’s lives healthier, safer and more fulfilling by helping detect, prevent, and treat disease, furthering scientific resea...
Compliance Ranges Comparison

OrthoSensor, now part of Stryker







Olympus Corporation






Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for OrthoSensor, now part of Stryker in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Olympus Corporation in 2026.
Incident History - OrthoSensor, now part of Stryker (X = Date, Y = Severity)
OrthoSensor, now part of Stryker cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Olympus Corporation (X = Date, Y = Severity)
Olympus Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

OrthoSensor, now part of Stryker

Olympus Corporation
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.