Comparison Overview
Kreissparkasse Traunstein-Trostberg

Kreissparkasse Traunstein-Trostberg
N/A
Last Update: 28/03/2026
Unsere Sparkasse wurde im Jahre 1863 gegründet und ist das größte selbstständige Kreditinstitut im Landkreis. Unser Geschäftsgebiet ist, mit Ausnahme der Gemeinde Schnaitsee, der gesamte Landkreis Traunstein mit rund 170.000 Einwohnern und einer Fläche von 1.534 qkm....

Fifth Third Bank
38 Fountain Square Plaza, Cincinnati, 45202, US
Last Update: 02/04/2026
At Fifth Third Bank, everything we do is rooted in our purpose: to improve the lives of our customers and the well-being of our communities. Since our founding in 1858, we’ve been committed to creating a better financial experience by empowering our customers and client...
Compliance Ranges Comparison

Kreissparkasse Traunstein-Trostberg







Fifth Third Bank






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Kreissparkasse Traunstein-Trostberg in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Fifth Third Bank in 2026.
Incident History - Kreissparkasse Traunstein-Trostberg (X = Date, Y = Severity)
Kreissparkasse Traunstein-Trostberg cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Fifth Third Bank (X = Date, Y = Severity)
Fifth Third Bank cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Kreissparkasse Traunstein-Trostberg

Fifth Third Bank
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.