Comparison Overview
Inspection générale Groupe BPCE

Inspection générale Groupe BPCE
110, Avenue de France, Paris, 75013, FR
Last Update: 01/01/2026
Rattachée au plus haut niveau du Groupe BPCE, l'Inspection générale assure le contrôle périodique de l'organisation, notamment du dispositif de contrôle interne, de la gestion et de la situation financière des établissements du Groupe, anime et pilote la Filière Audit d...

Banco Bci
125, Las Condes, Región Metropolitana, CL
Last Update: 06/09/2026
Porque el mundo que nos rodea se actualiza constantemente, porque tu decides hacer tu vida más simple: para entretenerte, para compartir con tu familia o para moverte por la ciudad. En Bci evolucionamos junto a ti, en este mundo donde todo se transforma una y otra vez, ...
Compliance Ranges Comparison

Inspection générale Groupe BPCE







Banco Bci






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Inspection générale Groupe BPCE in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Banco Bci in 2026.
Incident History - Inspection générale Groupe BPCE (X = Date, Y = Severity)
Inspection générale Groupe BPCE cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Banco Bci (X = Date, Y = Severity)
Banco Bci cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Inspection générale Groupe BPCE

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