Comparison Overview
BBVA em Portugal

BBVA em Portugal
Av. Liberdade, 222, Lisboa, 1250-148, PT
Last Update: 12/03/2026
At BBVA we are leading the transformation of banking worldwide, united in pursuing our goal of bringing the age of opportunity to everyone. Firmly focused on the future, our on-going digital transformation is already producing disruptive innovations that power our visio...

Santander
Avenida de Cantabria S/N, Boadilla del Monte, Madrid, ES, 28660
Last Update: 06/10/2026
Banco Santander (SAN SM) is a leading commercial bank, founded in 1857 and headquartered in Spain and one of the largest banks in the world by market capitalization. The group’s activities are consolidated into five global businesses: Retail & Commercial Banking, Openba...
Compliance Ranges Comparison

BBVA em Portugal







Santander






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for BBVA em Portugal in 2026.
Incidents vs Banking Industry Avg (This Year)
Santander has 98.02% more incidents than the average of all companies with at least one recorded incident.
Incident History - BBVA em Portugal (X = Date, Y = Severity)
BBVA em Portugal cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Santander (X = Date, Y = Severity)
Santander cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

BBVA em Portugal

Santander
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.