Comparison Overview
Smith+Nephew

Smith+Nephew
5 Hatters Lane, Watford, Hertfordshire, GB, WD18 8YE
Last Update: 01/04/2026
Smith+Nephew is a global medical technology company. We design and manufacture technology that takes the limits off living. We support healthcare professionals to return their patients to health and mobility, helping them to perform at their fullest potential. From our...

Alcon
Avenue Louis-Casaï 58, Geneva, Switzerland, CH, 1216
Last Update: 09/07/2026
Alcon helps people see brilliantly. As the global leader in eye care with a heritage spanning over 75 years, we offer the broadest portfolio of products to enhance sight and improve people’s lives. Our Surgical and Vision Care products touch the lives of more than 260 m...
Compliance Ranges Comparison

Smith+Nephew







Alcon






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

Smith+Nephew

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