Comparison Overview
BNP Paribas Factor España
BNP Paribas Factor España
Emilio Vargas, 4, MADRID, MADRID, ES, 28043
Last Update: 03/04/2026
Bnp Paribas Factor Spain is established in 2009 as a part of BNP Paribas Factoring Group which is the European Market Leader in Factoring with more than 50 years market experience.
Dubai Holding
Umm Suqeim Road, across from Madinat Jumeirah, Dubai, 66000 , AE
Last Update: 01/04/2026
Dubai Holding is a diversified global investment company that continues to power Dubai’s growth across 10 key sectors, including real estate, hospitality, leisure & entertainment, media, ICT, design, education, retail, manufacturing & logistics and science. Since 2004...
Compliance Ranges Comparison
BNP Paribas Factor España
Dubai Holding
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for BNP Paribas Factor España in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Dubai Holding in 2026.
Incident History - BNP Paribas Factor España (X = Date, Y = Severity)
BNP Paribas Factor España cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Dubai Holding (X = Date, Y = Severity)
Dubai Holding cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BNP Paribas Factor España
Dubai Holding
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: *.*.