Comparison Overview
WAI by BNP Paribas
WAI by BNP Paribas
16, Boulevard des Italiens, Paris, 75009, FR
Last Update: 18/03/2026
BNP Paribas a développé depuis plusieurs années une expertise reconnue et un ancrage fort dans l’écosystème innovation. La banque dispose en France du maillage le plus important et d’une offre complète pour accompagner toutes les entreprises qui innovent, quelle que soi...
Bancolombia
CARRERA 48 26 85 AV INDUSTRIALES, Medellín, CO
Last Update: 09/04/2026
Somos un grupo financiero latinoamericano que apoya los sueños de las personas y busca establecer con ellas relaciones duraderas, basadas en la confianza, la cercanía, el respeto, la inclusión y la calidez. Escuchar, pensar en el otro y ser sensible a sus necesidades...
Compliance Ranges Comparison
WAI by BNP Paribas
Bancolombia
Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for WAI by BNP Paribas in 2026.
Incidents vs Banking Industry Avg (This Year)
Bancolombia has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - WAI by BNP Paribas (X = Date, Y = Severity)
WAI by BNP Paribas cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Bancolombia (X = Date, Y = Severity)
Bancolombia cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
WAI by BNP Paribas
Bancolombia
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: *.*.