Comparison Overview
Landessparkasse zu Oldenburg

Landessparkasse zu Oldenburg
Oldenburg (Oldenburg), DE
Last Update: 31/01/2026
Für die Landessparkasse zu Oldenburg (LzO) steht die Nähe zu unseren Kundinnen und Kunden an erster Stelle. Das beweisen wir nicht nur mit unseren 109 Filialen vor Ort, wir nehmen uns auch Zeit für Gespräche auf Augenhöhe. Als älteste durchgehend geschäftstätige Sparkas...

UOB
80 Raffles Place, Singapore, 048624, SG
Last Update: 28/03/2026
We’re here to do Right By You. At UOB, we aspire to build a better future for the people and businesses in the region. Through our extensive network and suite of capabilities, we offer financial solutions to the people and businesses within, and connecting with ASE...
Compliance Ranges Comparison

Landessparkasse zu Oldenburg







UOB






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

Landessparkasse zu Oldenburg

UOB
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.