Comparison Overview
Sparkasse Langen-Seligenstadt
Sparkasse Langen-Seligenstadt
Frankfurter Straße 137, Seligenstadt, 63500, DE
Last Update: 21/04/2026
Mit unseren rund 600 Mitarbeiterinnen und Mitarbeitern sowie einer Bilanzsumme von rund 5 Milliarden Euro engagieren wir uns für die Menschen und Unternehmen im Kreis Offenbach. Als lokal verankertes Kreditinstitut zeigen wir uns verantwortlich für das Gemeinwohl und u...
Nomura
1-9-1 Nihonbashi, Tokyo, 103-8645, JP
Last Update: 02/04/2026
Nomura is a financial services group with an integrated global network. By connecting markets East & West, Nomura services the needs of individuals, institutions, corporates and governments through its four business divisions: Wealth Management, Investment Management, W...
Compliance Ranges Comparison
Sparkasse Langen-Seligenstadt
Nomura
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Sparkasse Langen-Seligenstadt in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Nomura in 2026.
Incident History - Sparkasse Langen-Seligenstadt (X = Date, Y = Severity)
Sparkasse Langen-Seligenstadt cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Nomura (X = Date, Y = Severity)
Nomura cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Sparkasse Langen-Seligenstadt
Nomura
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: *.*.