Comparison Overview
Sparkasse Uckermark

Sparkasse Uckermark
Georg-Dreke-Ring 62, Prenzlau, 17291, DE
Last Update: 02/04/2026
May we introduce ourselves? Welcome to Sparkasse Uckermark! Sparkasse Uckermark is one of the public credit institutions with a long tradition, because the savings bank system in the Uckermark district dates back to 1822. Sparkasse Uckermark is more than just an emplo...

Fifth Third Bank
38 Fountain Square Plaza, Cincinnati, 45202, US
Last Update: 02/04/2026
At Fifth Third Bank, everything we do is rooted in our purpose: to improve the lives of our customers and the well-being of our communities. Since our founding in 1858, we’ve been committed to creating a better financial experience by empowering our customers and client...
Compliance Ranges Comparison

Sparkasse Uckermark







Fifth Third Bank






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Sparkasse Uckermark in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Fifth Third Bank in 2026.
Incident History - Sparkasse Uckermark (X = Date, Y = Severity)
Sparkasse Uckermark cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Fifth Third Bank (X = Date, Y = Severity)
Fifth Third Bank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sparkasse Uckermark

Fifth Third Bank
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.