Comparison Overview
BNP Paribas Artegy
BNP Paribas Artegy
18, Rue Baudin, Levallois-Perret, Île-de-France, FR, 92300
Last Update: 01/04/2026
We are a commercial vehicle specialist with over 30 years’ experience and 10,000 vehicles under management in France. Our expertise means stability and success for your business. We understand that operating costs, compliance and vehicle uptime are of paramount importan...
OTP Group
Nádor u., Budapest, 1051, HU
Last Update: 31/03/2026
OTP Group is one of the fastest growing, leading independent banking groups in Central and Eastern Europe with a bridgehead in Central Asia. It operates in 11 countries - 10 in CEE region and 1 in Uzbekistan, employing nearly 40,000 people and providing universal finan...
Compliance Ranges Comparison
BNP Paribas Artegy
OTP Group
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for BNP Paribas Artegy in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for OTP Group in 2026.
Incident History - BNP Paribas Artegy (X = Date, Y = Severity)
BNP Paribas Artegy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - OTP Group (X = Date, Y = Severity)
OTP Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
BNP Paribas Artegy
OTP Group
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: *.*.