Comparison Overview
Sparkasse Bodensee
Sparkasse Bodensee
Charlottenstraße 2, Friedrichshafen, 88045, DE
Last Update: 26/03/2026
Hier entsteht Gutes. Wir sind kein fancy FinTech. Dafür sind wir hier – für euch vor Ort in der Bodensee-Region. Vom ersten Konto über die Finanzierung der eigenen vier Wände bis zur richtigen Altersvorsorge. Hier machen wir uns stark für alles, was wirklich zählt. Im L...
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
Sparkasse Bodensee
Security Bank Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Sparkasse Bodensee in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Security Bank Corporation in 2026.
Incident History - Sparkasse Bodensee (X = Date, Y = Severity)
Sparkasse Bodensee 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
Sparkasse Bodensee
Security Bank Corporation
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.