Comparison Overview
Commerzbank AG
Commerzbank AG
Kaiserstraße 16, Frankfurt am Main, 60311, DE
Last Update: 01/04/2026
Commerzbank is the leading bank for the German Mittelstand and a strong partner for around 24,000 corporate client groups. In addition, it supports private and small-business customers in Germany with more than €400 billion assets under management. The Bank’s two Busine...
CIC
6, Avenue de Provence, Paris, Île-de-France, FR, 75009
Last Update: 01/04/2026
CIC is the fourth largest banking group in France, consisting of seven regional banks which operate across France through a network of 1,844 branches employing 24,000 staff. CIC's customer base includes 2.7 million retail clients. One in eleven self-employed professiona...
Compliance Ranges Comparison
Commerzbank AG
CIC
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Commerzbank AG in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for CIC in 2026.
Incident History - Commerzbank AG (X = Date, Y = Severity)
Commerzbank AG cyber incidents detection timeline including parent company and subsidiaries.
Incident History - CIC (X = Date, Y = Severity)
CIC cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Commerzbank AG
CIC
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: *.*.