Comparison Overview
Absa Corporate and Investment Banking
Absa Corporate and Investment Banking
15 Alice Lane, Johannesburg, Gauteng, 2000, ZA
Last Update: 22/01/2026
We stand with you to make your vision a reality. With a relentless African spirit and distinct client focus, we have become a leading corporate and investment bank in and for our continent. We’re a forward-thinking African business with a local presence in 10 countries...
NN Group
Schenkkade 65, Den Haag, Zuid-Holland, NL, 2595
Last Update: 01/04/2026
NN Group is an international financial services company, active in 10 countries, with a strong presence in a number of European countries and Japan. We are rooted in the Netherlands and have a rich history spanning 180 years. With our 16,000 colleagues, NN Group provid...
Compliance Ranges Comparison
Absa Corporate and Investment Banking
NN Group
Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Absa Corporate and Investment Banking in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for NN Group in 2026.
Incident History - Absa Corporate and Investment Banking (X = Date, Y = Severity)
Absa Corporate and Investment Banking cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NN Group (X = Date, Y = Severity)
NN Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Absa Corporate and Investment Banking
NN 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: *.*.