Comparison Overview
Louvre Banque Privée
Louvre Banque Privée
48, Rue du Louvre, Paris, Île-de-France, 75001, FR
Last Update: 12/03/2026
Louvre Banque Privée, créée en 1963 et filiale de La Banque Postale, propose une offre globale à destination d’une clientèle patrimoniale de familles, chef d’entreprises, dirigeants et family offices. Unique par son modèle de banque privée ancrée dans les territoires, L...
HDFC Bank Limited
N/A
Last Update: 30/05/2026
HDFC Bank Limited (also known as HDB) is an Indian banking and financial services company headquartered in Mumbai. It is India's largest private sector bank by assets and world's fifth largest bank by market capitalisation as of August 2023, following its takeover of pa...
Compliance Ranges Comparison
Louvre Banque Privée
HDFC Bank Limited
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Louvre Banque Privée in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for HDFC Bank Limited in 2026.
Incident History - Louvre Banque Privée (X = Date, Y = Severity)
Louvre Banque Privée cyber incidents detection timeline including parent company and subsidiaries.
Incident History - HDFC Bank Limited (X = Date, Y = Severity)
HDFC Bank Limited cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Louvre Banque Privée
HDFC Bank Limited
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: *.*.