Comparison Overview
Arthrex Polska

Arthrex Polska
Karczunkowska, Warszawa, 02-871, PL
Last Update: 01/04/2026
Arthrex jest prywatną firmą, założoną w 1981 roku. Jesteśmy producentem wyrobów medycznych o globalnym zasięgu oraz liderem innowacji i edukacji medycznej w dziedzinie ortopedii. Przedsiębiorstwo Arthrex Polska powstało w 2012 r. i od tego czasu nieustannie umacnia sw...

Alcon
Avenue Louis-Casaï 58, Geneva, 1216, CH
Last Update: 13/09/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

Arthrex Polska







Alcon






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

Arthrex Polska

Alcon
FAQ
Latest Global CVEs
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
Improper certificate validation in Microsoft Partner Center allows an unauthorized attacker to elevate privileges over a network.
Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.