Comparison Overview
VPBank

VPBank
89 Lang Ha, Dong Da, Ha Noi, Hanoi, 100000, VN
Last Update: 29/01/2026
VPBank has set its 3rd five-year (2022-2026) development strategy goal to become a bank with a solid position in the top 3 leading banks in Vietnam and one of the top 100 largest banks in Asia. The achievements of the first two development phases (2012-2017 and 2018-20...

SEB
Kungsträdgårdsgatan 8, Stockholm, Stockholm, SE, 10640
Last Update: 01/04/2026
SEB is a leading northern European financial services group with a strong belief that entrepreneurial minds and innovative companies are key in creating a better world. SEB takes a long-term perspective and supports its customers in good times and bad. In Sweden and ...
Compliance Ranges Comparison

VPBank







SEB






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

VPBank

SEB
FAQ
Latest Global CVEs
phpMyFAQ before 4.1.5 contains a privilege escalation vulnerability in GroupController::updatePermissions that allows GROUP_EDIT administrators to grant arbitrary rights to groups without verifying they hold those rights themselves. A delegated administrator can exploit this by assigning high-value permissions to a group they belong to, inheriting those rights and escalating privileges up to full administrative control.
n8n before 2.25.7 and 2.26.x before 2.26.2 contains an abstract syntax tree (AST) security validator bypass in the Python Code node. An authenticated user with permission to create or modify workflows containing a Python Code node can bypass the validator and access the task executor module namespace. The issue only affects self-hosted instances where the Python Task Runner is enabled; where N8N_BLOCK_RUNNER_ENV_ACCESS is configured to allow it, this can disclose environment variables accessible to the task runner process.
Grav CMS before 2.0.0-beta.2 contains multiple code-execution vulnerabilities. Three unsafe unserialize() calls - in Scheduler\JobQueue, Framework\Cache\Adapter\FileCache, and Session - deserialize untrusted data without restricting allowed classes, enabling PHP object injection and, via a gadget chain, arbitrary code execution where an attacker controls the serialized input. Additionally, InstallCommand's git clone operation passes the branch, url, and path parameters into a shell command without escaping, allowing OS command injection via plugin/theme installation (which requires admin access). A Twig security blocklist bypass (server-side template injection) is also present. The issues are fixed in 2.0.0-beta.2.
Storage Concentrator (SC & SCVM) contains a command injection vulnerability within the debug.pl script that is reachable without authentication. A remote attacker can submit a specially crafted HTTP request containing a malicious payload that is processed without adequate input sanitization, resulting in arbitrary command execution with root-level privileges on the underlying system.
Storage Concentrator (SC & SCVM) contains a command injection vulnerability in the ms_service.pl service, which listens on TCP port 9000 by default and accepts custom network packets to perform device actions. An unauthenticated remote attacker can send a specially crafted packet containing a malicious payload that is processed without adequate sanitization, resulting in arbitrary command execution with root-level privileges.