Comparison Overview
Stadtsparkasse Cuxhaven
Stadtsparkasse Cuxhaven
Rohdestraße 6, Cuxhaven, Cuxhaven, DE, 27472
Last Update: 19/01/2026
Wir, die Stadtsparkasse Cuxhaven sind nicht nur für unsere Kund:innen, sondern auch für unsere 200 Mitarbeitenden ein wertvoller und zuverlässiger Partner. Unser Engagement in der Region und die Nähe zu den Menschen in dieser zeichnet uns aus. Mit einer Bilanzsumme von ...
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
Stadtsparkasse Cuxhaven
alrajhi bank
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Stadtsparkasse Cuxhaven in 2026.
Incidents vs Banking Industry Avg (This Year)
alrajhi bank has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Stadtsparkasse Cuxhaven (X = Date, Y = Severity)
Stadtsparkasse Cuxhaven 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
Stadtsparkasse Cuxhaven
alrajhi bank
FAQ
Latest Global CVEs
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to exposure of session tokens in the HTML response.
IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 could allow a remote authenticated attacker to obtain sensitive information due to an XML external entity (XXE) injection flaw.
IBM Aspera Enterprise WebApps 1.0.0 through 1.0.6 could allow a local attacker to obtain sensitive information due to cleartext transmission of sensitive information.
IBM Planning Analytics 2.0, and 2.1 could allow a remote authenticated attacker to execute arbitrary code due to a stack-based buffer overflow.
IBM DataStage on Cloud Pak for Data 5.4.0.0 can allow a man-in-the-middle attacker to present a forged TLS certificate, intercept the connection, and capture the IAM bearer Authorization header automatically attached by the session adapter. The captured token grants full platform-scope tenant API access, enabling the attacker to read and manipulate the victim's DataStage projects, flows, assets, and pipeline definitions. This is client-side SDK code running on the user's own machine, so exploitation requires an external network interceptor rather than a co-tenant in the shared cluster.