Comparison Overview
Ecobank International SA
Ecobank International SA
76, Route de la Demi-Lune, Puteaux, 92800, FR
Last Update: 19/03/2026
La filiale EBI SA - Ecobank International a été créée à Paris en 2008 pour être la tête de pont du développement du groupe Ecobank à l’international et devenir une référence dans le financement du commerce international et la gestion des flux financiers entre l’Afrique ...
BNP Paribas Fortis
Rue Montagne du Parc 3, Brussels, 1000, BE
Last Update: 02/04/2026
For over 200 years, BNP Paribas Fortis has helped drive the growth and prosperity of Belgium’s economy and communities. The mission of our 12,000 colleagues is clear: be the trusted financial partner for four million individual customers, businesses and organisations. W...
Compliance Ranges Comparison
Ecobank International SA
BNP Paribas Fortis
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Ecobank International SA in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for BNP Paribas Fortis in 2026.
Incident History - Ecobank International SA (X = Date, Y = Severity)
Ecobank International SA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BNP Paribas Fortis (X = Date, Y = Severity)
BNP Paribas Fortis cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Ecobank International SA
BNP Paribas Fortis
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: *.*.