Comparison Overview
Volkswagen Pon Financial Services
Volkswagen Pon Financial Services
Saturnus 1, Amersfoort, 3824 ME, NL
Last Update: 04/03/2026
Volkswagen Pon Financial Services - Een lange naam, maar om sterke merken kun je niet heen. Zij vormen onze roots en hebben de basis gelegd voor het brede gamma aan financiële diensten dat we u kunnen bieden. Door ons specialisme, vakkennis en ervaring kunnen we ied...
Old Mutual
107 Rivonia Rd, Johannesburg, ZA
Last Update: 02/04/2026
Old Mutual Limited is a listed company on the Johannesburg Stock Exchange and has secondary listings on the London, Malawi, Namibia and Zimbabwe stock exchanges. As a Pan-African financial services company, we are focused on Africa, her needs and her people. Together w...
Compliance Ranges Comparison
Volkswagen Pon Financial Services
Old Mutual
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Volkswagen Pon Financial Services in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Old Mutual in 2026.
Incident History - Volkswagen Pon Financial Services (X = Date, Y = Severity)
Volkswagen Pon Financial Services cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Old Mutual (X = Date, Y = Severity)
Old Mutual cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Volkswagen Pon Financial Services
Old Mutual
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: *.*.