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...
Security Bank Corporation
6776 Ayala Avenue, Makati, 1200, PH
Last Update: 02/04/2026
Security Bank is one of the Philippines’ best-capitalized private domestic universal banks. Established in 1951 and publicly listed with the Philippine Stock Exchange (PSE: SECB) in 1995, our major businesses cover retail, corporate, commercial, and business (MSME) bank...
Compliance Ranges Comparison
Santander Portugal
Security Bank Corporation
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 Security Bank Corporation in 2026.
Incident History - Santander Portugal (X = Date, Y = Severity)
Santander Portugal cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Security Bank Corporation (X = Date, Y = Severity)
Security Bank Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Santander Portugal
Security Bank Corporation
FAQ
Latest Global CVEs
A vulnerability was identified in Databend up to 1.2.881 on HTTP. This affects the function ClientSessionManager::state_key of the file src/query/service/src/servers/http/v1/session/client_session_manager.rs of the component Tenant Handler. The manipulation leads to authorization bypass. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The pull request to fix this issue awaits acceptance.
A vulnerability was determined in VoltAgent up to 2.1.17. Affected by this issue is the function handleGetMemoryConversation of the file packages/server-core/src/handlers/memory.handlers.ts of the component Memory REST API. Executing a manipulation of the argument conversationId can lead to improper authorization. The attack may be performed from remote. This attack is characterized by high complexity. The exploitation is known to be difficult. The exploit has been publicly disclosed and may be utilized. The pull request to fix this issue awaits acceptance.
A vulnerability was found in SimStudioAI sim up to 0.6.92. Affected by this vulnerability is an unknown functionality in the library apps/sim/lib/core/security/deployment.ts of the component Password Protection Handler. Performing a manipulation results in use of weak hash. The attack is possible to be carried out remotely. The attack's complexity is rated as high. The exploitation appears to be difficult. The exploit has been made public and could be used. The pull request to fix this issue awaits acceptance.
A vulnerability has been found in RAGapp up to 0.1.5. Affected is the function FileHandler.upload_file/FileHandler.remove_file of the file src/ragapp/backend/controllers/files.py of the component Knowledge File Handler. Such manipulation leads to path traversal. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.
A flaw has been found in khoj-ai khoj up to 2.0.0-beta.28. This impacts an unknown function of the file src/khoj/routers/api_chat.py of the component Conversation Sharing Handler. This manipulation of the argument conversation.agent causes incorrect authorization. Remote exploitation of the attack is possible. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.