Comparison Overview
ZEISS Medical Technology

ZEISS Medical Technology
Goeschwitzer Strasse 51-52, Jena, 07745, DE
Last Update: 08/12/2025
Our aim is contributing to progress in medical technology and helping healthcare professionals all over the world to improve their patients' quality of life. With a special focus on ophthalmology, ophthalmic surgery and visualization systems in the field of microsurge...

Stryker
2825 Airview Boulevard, Kalamazoo, 49002, US
Last Update: 11/09/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

ZEISS Medical Technology







Stryker






Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for ZEISS Medical Technology in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
Stryker has 1566.67% more incidents than the average of all companies with at least one recorded incident.
Incident History - ZEISS Medical Technology (X = Date, Y = Severity)
ZEISS Medical Technology 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

ZEISS Medical Technology

Stryker
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.