Comparison Overview
BGL BNP Paribas

BGL BNP Paribas
60 avenue J. F. Kennedy, Luxembourg, L-2951, LU
Last Update: 01/04/2026
Founded in 1919, BGL BNP Paribas now occupies the position of market leader in its home market and has extended its business throughout the Grande Région, including the areas around Luxembourg's borders. It has played an active part in Luxembourg's emergence as an ...

Banco Azteca
Av. Insurgentes Sur 3579, México, 14020, MX
Last Update: 15/09/2026
Banco Azteca es un banco mexicano fundado en el año 2002 y es una compañía de Grupo Salinas del empresario Mexicano Ricardo Salinas Pliego. Cuenta con 1,500 sucursales en México, Panamá, Argentina, Honduras, El Salvador, Brasil y Perú; es uno de los dos bancos más grand...
Compliance Ranges Comparison

BGL BNP Paribas







Banco Azteca






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

BGL BNP Paribas

Banco Azteca
FAQ
Latest Global CVEs
The web management service in affected RouterOS versions contains an integer underflow in its HTTP request body handling that is reachable before authentication. This can be leveraged by an unauthenticated network attacker to achieve arbitrary code execution as root, or to cause a denial of service, using a single crafted request.
Denuvo Anti-Tamper through 2026-03-04 allows bypass of a hypervisor presence check via CPUID interception (SimpleSvm.sys on AMD; hyperkd.sys and hyperhv.dll on Intel).
PeaZip before 11.3.0, in a non-default configuration, is vulnerable to OS command injection via a filename in an archive because "quotation character already used in the string" is mishandled.
Zilliz Attu before 3.0.0 has a Playground feature that does not require authentication for proxying arbitrary HTTP and HTTPS requests to URLs on the public internet.
The Playground feature of Zilliz Attu before 3.0.0 allows SSRF (proxying of requests to private IP addresses).