Comparison Overview
THINK Surgical

THINK Surgical
47201 Lakeview Blvd, None, Fremont, CA, US, 94538
Last Update: 28/03/2026
THINK Surgical, Inc., is a privately held U.S.-based technology innovator that develops and markets orthopedic robots. THINK Surgical robots are open platforms providing support for implant brands from multiple manufacturers, enabling the choice of implant to be driven ...

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

THINK Surgical







Smith+Nephew






Benchmark & Cyber Underwriting Signals
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for THINK Surgical in 2026.
Incidents vs Medical Equipment Manufacturing Industry Avg (This Year)
No incidents recorded for Smith+Nephew in 2026.
Incident History - THINK Surgical (X = Date, Y = Severity)
THINK Surgical 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

THINK Surgical

Smith+Nephew
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)