Comparison Overview
Sparkasse Bochum
Sparkasse Bochum
Dr.-Ruer-Platz, Bochum, 44787, DE
Last Update: 01/04/2026
Als lokal verwurzeltes Kreditinstitut mit engem Bezug zur Realwirtschaft steht die Sparkasse Bochum Privatkunden und Unternehmen als zuverlässiger und sicherer Finanzierungspartner zur Seite. Seit dem Jahr 1838 berät und unterstützt die Sparkasse Bochum die Bürgerinnen ...
alrajhi bank
King Fahad Branch Road, Al Rajhi Tower, Riyadh, Riyadh Province, SA, 11411
Last Update: 04/05/2026
Founded in 1957, Al Rajhi Bank is one of the largest Islamic banks in the world with total assets of SR 384 billion (US$ 102 billion), a paid up capital of SR 25 billion (US$ 6.66 billion) and an employee base of over 9,600 associates. With over 58 years of experience i...
Compliance Ranges Comparison
Sparkasse Bochum
alrajhi bank
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Sparkasse Bochum in 2026.
Incidents vs Banking Industry Avg (This Year)
alrajhi bank has 7.41% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Sparkasse Bochum (X = Date, Y = Severity)
Sparkasse Bochum cyber incidents detection timeline including parent company and subsidiaries.
Incident History - alrajhi bank (X = Date, Y = Severity)
alrajhi bank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sparkasse Bochum
alrajhi 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.