Comparison Overview
Stratasys Medical

Stratasys Medical
Rehovot, IL
Last Update: 05/03/2026
Stratasys is a global leader in additive technology solutions for a variety of industries including Medical. For over 30 years, a deep and ongoing focus on customers’ business requirements has fueled purposeful innovations that create new value. Corporate headquarters: ...

Smith+Nephew
5 Hatters Lane, Watford, Hertfordshire, GB, WD18 8YE
Last Update: 12/09/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...
Compliance Ranges Comparison

Stratasys Medical







Smith+Nephew






Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Stratasys Medical in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Smith+Nephew in 2026.
Incident History - Stratasys Medical (X = Date, Y = Severity)
Stratasys Medical cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Smith+Nephew (X = Date, Y = Severity)
Smith+Nephew cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Stratasys Medical

Smith+Nephew
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.