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...
Regions Bank
1900 5th Ave N, Birmingham, Alabama, US, 35203
Last Update: 02/04/2026
Regions Financial Corporation is a member of the S&P 500 Index and is one of the nation’s largest full-service providers of consumer and commercial banking, wealth management, and mortgage products and services. Regions serves customers across the South, Midwest and Tex...
Compliance Ranges Comparison
Santander Portugal
Regions Bank
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 Regions Bank in 2026.
Incident History - Santander Portugal (X = Date, Y = Severity)
Santander Portugal cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Regions Bank (X = Date, Y = Severity)
Regions Bank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Santander Portugal
Regions Bank
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.