Comparison Overview
Sparkasse Zollernalb
Sparkasse Zollernalb
Friedrichstr. 3, Balingen, 72336, DE
Last Update: 25/03/2026
Für die Sparkasse Zollernalb engagieren sich rund 530 Beschäftigte. Wir gehören zu den eigenkapitalstärksten Sparkassen Baden-Württembergs. Als lokal verwurzeltes Finanzinstitut übernehmen wir gesellschaftliche Verantwortung für die Menschen und den Landkreis.
BMO U.S.
320 S Canal St, Chicago, Illinois, US, 60661
Last Update: 04/04/2026
We’re a bank, but there’s more to it than that. We're a top ten bank in North America and have been serving our customers since 1817. BMO provides personal and commercial banking, global markets and investment banking services to 13 million customers and clients. And w...
Compliance Ranges Comparison
Sparkasse Zollernalb
BMO U.S.
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Sparkasse Zollernalb in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for BMO U.S. in 2026.
Incident History - Sparkasse Zollernalb (X = Date, Y = Severity)
Sparkasse Zollernalb cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BMO U.S. (X = Date, Y = Severity)
BMO U.S. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sparkasse Zollernalb
BMO U.S.
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.