Comparison Overview
Sparkasse Bad Hersfeld - Rotenburg
Sparkasse Bad Hersfeld - Rotenburg
Dudenstraße 15, Bad Hersfeld, 36251, DE
Last Update: 28/03/2026
Herrlich normal! Mit dem Herz am rechten Fleck: Spaß am Job und auch am Leben haben. Ohne Schnickschnack, Könner ohne Arroganz. Das sind Menschen bei unserer Sparkasse: Einfach genial, weil herrlich normal. Wir sind die Sparkasse Bad Hersfeld-Rotenburg!
KeyBank
127 Public Square, Cleveland , Ohio, US, 44114
Last Update: 07/09/2026
At KeyBank we’ve made a promise to our clients that they will always have a champion in us. To deliver on our promise, we’re committed to building a team of engaged employees who do the right thing for our clients and shareholders, and help them achieve financial wellne...
Compliance Ranges Comparison
Sparkasse Bad Hersfeld - Rotenburg
KeyBank
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Sparkasse Bad Hersfeld - Rotenburg in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for KeyBank in 2026.
Incident History - Sparkasse Bad Hersfeld - Rotenburg (X = Date, Y = Severity)
Sparkasse Bad Hersfeld - Rotenburg cyber incidents detection timeline including parent company and subsidiaries.
Incident History - KeyBank (X = Date, Y = Severity)
KeyBank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sparkasse Bad Hersfeld - Rotenburg
KeyBank
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