Comparison Overview
Sparkasse Regensburg
Sparkasse Regensburg
Lilienthalstraße 5, Regensburg, 93049, DE
Last Update: 21/04/2026
Wir machen es den Menschen einfach, ihr Leben besser zu gestalten. Auch als Arbeitgeber. Als Marktführer ist das Herzstück unserer Unternehmensphilosophie unsere Kundennähe und die Regionalität. Unsere Beschäftigten beraten mit Leidenschaft unseren Kundenkreis in d...
American Express
World Financial Center, 200 Vesey Street, New York, 10285, US
Last Update: 07/05/2026
At American Express, we know that with the right backing, people and businesses have the power to progress in incredible ways. Whether we’re supporting our customers’ financial confidence to move ahead, taking commerce to new heights, or encouraging people to explore th...
Compliance Ranges Comparison
Sparkasse Regensburg
American Express
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Sparkasse Regensburg in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for American Express in 2026.
Incident History - Sparkasse Regensburg (X = Date, Y = Severity)
Sparkasse Regensburg cyber incidents detection timeline including parent company and subsidiaries.
Incident History - American Express (X = Date, Y = Severity)
American Express cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sparkasse Regensburg
American Express
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.