Comparison Overview
ClearBalance Healthcare

ClearBalance Healthcare
3636 Nobel Drive, San Diego, 92122, US
Last Update: 03/04/2026
ClearBalance: The US Market Leader in Patient Financing At ClearBalance, we are transforming the way healthcare systems and patients manage medical expenses. As the #1 patient financing partner in the US, we provide interest-free, flexible repayment plans that make hea...

Banco Davivienda
Avenida Calle 26 68C-61, Bogota, 110931, CO
Last Update: 16/09/2026
En Davivienda creemos en un mundo financiero sin barreras que facilite la vida a las personas, las empresas, las ciudades y municipios. Por esta razón hoy somos más de 19.000 personas innovando y creando cada día soluciones y ofertas exclusivas para 10 millones de clien...
Compliance Ranges Comparison

ClearBalance Healthcare







Banco Davivienda






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for ClearBalance Healthcare in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Banco Davivienda in 2026.
Incident History - ClearBalance Healthcare (X = Date, Y = Severity)
ClearBalance Healthcare cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Banco Davivienda (X = Date, Y = Severity)
Banco Davivienda cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ClearBalance Healthcare

Banco Davivienda
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.