Comparison Overview
Global Atlantic
Global Atlantic
30 Hudson Yards, 500 West 33rd Street, New York, NY, US, 10001
Last Update: 29/03/2026
Global Atlantic is a leading provider of retirement security and investment solutions with operations in the U.S., Bermuda, and Japan. As a wholly-owned subsidiary of KKR (NYSE: KKR), a leading global investment firm, Global Atlantic combines deep insurance expertise wi...
Aflac
1932 Wynnton Rd, Columbus, 31999, US
Last Update: 30/06/2026
Over 50 Million people worldwide have chosen Aflac because of our commitment to providing customers with the confidence that comes from knowing they have assistance in being prepared for whatever life may bring. With Aflac, whether you're a large business or a small o...
Compliance Ranges Comparison
Global Atlantic
Aflac
Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Global Atlantic in 2026.
Incidents vs Insurance Industry Avg (This Year)
Aflac has 88.68% more incidents than the average of all companies with at least one recorded incident.
Incident History - Global Atlantic (X = Date, Y = Severity)
Global Atlantic cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Aflac (X = Date, Y = Severity)
Aflac cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Global Atlantic
Aflac
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: *.*.