Comparison Overview
Banco de Chile

Banco de Chile
Ahumada 251, Santiago, Santiago, 8320206, CL
Last Update: 15/09/2026
Somos una Corporación líder y comprometida con el país que brinda servicios financieros de excelencia a cada segmento de clientes. Buscamos permanentemente ser el mejor Banco para ellos, ser el mejor lugar para trabajar y ser la mejor inversión para nuestros accionistas...

BNP Paribas
16 boulevard des Italiens, Paris, FR, 75009
Last Update: 12/09/2026
BNP Paribas is a leading bank in Europe with an international reach. It has a presence in 64 countries, with more than 178,000 employees, including more than 144,000 in Europe. BNP Paribas holds leading positions in its three major operating divisions: ⚆ Commercial, P...
Compliance Ranges Comparison

Banco de Chile







BNP Paribas






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Banco de Chile in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for BNP Paribas in 2026.
Incident History - Banco de Chile (X = Date, Y = Severity)
Banco de Chile cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BNP Paribas (X = Date, Y = Severity)
BNP Paribas cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Banco de Chile

BNP Paribas
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.