Comparison Overview
Keralty
Keralty
Calle 100 # 11b -67, Bogota, 110111, CO
Last Update: 05/09/2026
Anteriormente Organización Sanitas Internacional, Keralty es un grupo empresarial de valor en salud, con más de 40 años de experiencia conformado por empresas de aseguramiento y prestación de servicios de salud y una red propia hospitalaria y asistencial. También form...
University of Maryland Medical System
22 S. Greene St, Baltimore, MD, US, 21201
Last Update: 10/09/2026
The University of Maryland Medical System (UMMS) was created in 1984 when the state-owned University Hospital became a private, nonprofit organization. It has evolved into a multi-hospital system with academic, community and specialty service missions reaching every par...
Compliance Ranges Comparison
Keralty
University of Maryland Medical System
Benchmark & Cyber Underwriting Signals
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for Keralty in 2026.
Incidents vs Hospitals and Health Care Industry Avg (This Year)
No incidents recorded for University of Maryland Medical System in 2026.
Incident History - Keralty (X = Date, Y = Severity)
Keralty cyber incidents detection timeline including parent company and subsidiaries.
Incident History - University of Maryland Medical System (X = Date, Y = Severity)
University of Maryland Medical System cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Keralty
University of Maryland Medical System
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)