Comparison Overview
The University of Texas Medical Branch
The University of Texas Medical Branch
301 University Blvd, Galveston, Texas, US, 77550
Last Update: 01/04/2026
The first academic health center in Texas opened its doors in 1891 and today has four campuses, five health sciences schools, seven institutes for advanced study, a research enterprise that includes one of only two national laboratories dedicated to the safe study of in...
Mercy
15740 South Outer Forty Road, Chesterfield, 63017 , US
Last Update: 29/03/2026
Mercy, one of the 15 largest U.S. health systems and named the top large system in the U.S. for excellent patient experience by NRC Health, serves millions annually with nationally recognized care and one of the nation’s largest and highest performing Accountable Care O...
Compliance Ranges Comparison
The University of Texas Medical Branch
Mercy
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for The University of Texas Medical Branch in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Mercy in 2026.
Incident History - The University of Texas Medical Branch (X = Date, Y = Severity)
The University of Texas Medical Branch cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Mercy (X = Date, Y = Severity)
Mercy cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
The University of Texas Medical Branch
Mercy
FAQ
Latest Global CVEs
Improper access control in Microsoft Edge for Android allows an unauthorized attacker to bypass a security feature over a network.
A security vulnerability has been detected in NousResearch hermes-agent up to 2026.4.30. Affected is the function GatewayStreamConsumer._filter_and_accumulate of the file gateway/stream_consumer.py of the component Streaming Reasoning Tag Filter. The manipulation leads to improper handling of case sensitivity. The attack may be initiated remotely. The attack's complexity is rated as high. The exploitability is told to be difficult. The exploit has been disclosed publicly and may be used. The project decided to not implement a dedicated fix: "[T]he analysis and the fix are both sound. It just lands below the bar for the maintenance cost of a duplicated scrub path."
- https://gist.github.com/YLChen-007/2229e5505bcbb3e15a7ae8fba4c4be37
- https://github.com/NousResearch/hermes-agent/
- https://github.com/NousResearch/hermes-agent/issues/27288
- https://github.com/NousResearch/hermes-agent/pull/28631#issuecomment-4622188016
- https://vuldb.com/cve/CVE-2026-14617
- https://vuldb.com/submit/844654
- https://vuldb.com/vuln/376134
- https://vuldb.com/vuln/376134/cti
Insufficient ui warning of dangerous operations in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform spoofing over a network.
Improper neutralization of input during web page generation ('cross-site scripting') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to perform spoofing over a network.
Relative path traversal in Microsoft Edge for Android allows an unauthorized attacker to disclose information locally.