Comparison Overview
Sparkasse Westholstein

Sparkasse Westholstein
Dithmarscher Platz 2, Itzehoe, 25524, DE
Last Update: 29/03/2026
Moin! 👋🏻 Wir sind die Sparkasse Westholstein und engagieren uns mit unserem 550-köpfigen Team in der Energiewenderegion Dithmarschen und Steinburg für die Bedürfnisse unserer Kund:innen. Als Mitglied der erfolgreichen S-Finanzgruppe sind wir seit über 200 Jahren ein ...

First Abu Dhabi Bank (FAB)
Abu Dhabi, 6316, AE
Last Update: 05/09/2026
FAB, the UAE’s largest bank and one of the world’s largest financial institutions offers a an extensive range of tailor-made solutions, and products and services, to provide a customised banking experience. Through its strategic offerings, it looks to meet the banking n...
Compliance Ranges Comparison

Sparkasse Westholstein







First Abu Dhabi Bank (FAB)






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Sparkasse Westholstein in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for First Abu Dhabi Bank (FAB) in 2026.
Incident History - Sparkasse Westholstein (X = Date, Y = Severity)
Sparkasse Westholstein cyber incidents detection timeline including parent company and subsidiaries.
Incident History - First Abu Dhabi Bank (FAB) (X = Date, Y = Severity)
First Abu Dhabi Bank (FAB) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sparkasse Westholstein

First Abu Dhabi Bank (FAB)
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout