Comparison Overview
Rheinhessen Sparkasse

Rheinhessen Sparkasse
Bahnhofstraße 1, Mainz, 55116, DE
Last Update: 28/03/2026
Das erste Kreditinstitut in Rheinhessen Seit 1827 versorgen wir die Menschen in unserer Region mit Finanzdienstleistungen und unterstützen die heimische Wirtschaft. Als gut vernetzter Bestandteil der Region von Rhein und Reben sind wir mit unseren Standorten, unserer I...

HDB Financial Services Ltd.
HDB House, Tukaram Sandam Marg, Mumbai, 400057, IN
Last Update: 01/04/2026
HDB Financial Services (HDBFS) is a leading Non-Banking Financial Company (NBFC) that caters to the growing needs of an Aspirational India, serving both Individual & Business Clients The lines of business include - Lending and BPO Services. Incorporated in 2007, HDB is ...
Compliance Ranges Comparison

Rheinhessen Sparkasse







HDB Financial Services Ltd.






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

Rheinhessen Sparkasse

HDB Financial Services Ltd.
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: *.*.