Comparison Overview
Santander Portugal

Santander Portugal
Rua do Ouro, 88, Lisboa, Lisboa, 1100-063 LISBOA, PT
Last Update: 19/03/2026
Somos um Banco de referência no sector financeiro nacional, com uma ampla base de clientes e uma rede de balcões distribuídos por todo o país. A nossa atividade, centrada na banca comercial, prossegue uma estratégia de proximidade ao cliente, privilegiando a oferta de...

Banamex
Av. Actuario Roberto Medellín No. 800, Mexico, 01210, MX
Last Update: 02/04/2026
En Banamex una palabra nos ha definido durante nuestra historia: Estar. Estar es acompañar. Estar es avanzar juntos. Acompañar para forjar relaciones auténticas, duraderas, significativas, que nos den confianza y nos impulsen a alcanzar aquello que es importante para ...
Compliance Ranges Comparison

Santander Portugal







Banamex






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

Santander Portugal

Banamex
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.