Comparison Overview
AEG Global Partnerships - International
AEG Global Partnerships - International
King Street, london, GB
Last Update: 01/03/2026
AEG Global Partnerships oversees the worldwide sales and servicing of sponsorships for AEG’s entire portfolio of assets. Creating customised and innovative marketing programs for established and emerging brands it has created some of the most iconic brand partnerships i...
Entain
London, GB
Last Update: 01/04/2026
Welcome to Entain. Our journey as Entain began when we evolved from GVC Holdings on 9th December 2020, but our brands have been paving the way and making history since the 1880s. Today, we’re one of the world’s largest sports betting and gaming entertainment groups ...
Compliance Ranges Comparison
AEG Global Partnerships - International
Entain
Benchmark & Cyber Underwriting Signals
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for AEG Global Partnerships - International in 2026.
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for Entain in 2026.
Incident History - AEG Global Partnerships - International (X = Date, Y = Severity)
AEG Global Partnerships - International cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Entain (X = Date, Y = Severity)
Entain cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AEG Global Partnerships - International
Entain
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: *.*.