Comparison Overview
Borgess Health

Borgess Health
1521 Gull Road, Kalamazoo, Michigan, 49048, US
Last Update: 30/01/2026
Based in Kalamazoo, we provide care for nearly 1 million people annually in cardiac, neurologic, orthopedic, vascular and bariatric services, among others. We are one of the region’s largest health systems and employers and have been serving as part of Ascension, the na...

Johnson & Johnson MedTech
1 Johnson and Johnson Plaza, New Brunswick, New Jersey, US, 08901
Last Update: 01/04/2026
At Johnson & Johnson MedTech, we are working to solve the world’s most pressing healthcare challenges through innovations at the intersection of biology and technology. With deep expertise in surgery, orthopaedics, cardiovascular, and vision, we design healthcare soluti...
Compliance Ranges Comparison

Borgess Health







Johnson & Johnson MedTech






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Borgess Health in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Johnson & Johnson MedTech in 2026.
Incident History - Borgess Health (X = Date, Y = Severity)
Borgess Health cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Johnson & Johnson MedTech (X = Date, Y = Severity)
Johnson & Johnson MedTech cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Borgess Health

Johnson & Johnson MedTech
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.