Comparison Overview
AEG
AEG
800 W. Olympic Boulevard, Los Angeles, 90015, US
Last Update: 11/12/2025
From epic concerts to premier music festivals to heart-stopping sporting events, AEG has been giving the world reason to cheer for more than 20 years. Headquartered in Los Angeles, CA, we are the world’s leading sports and live entertainment company and operate on five ...
The Walt Disney Company
The Walt Disney Company, Burbank, 91521, US
Last Update: 03/06/2026
The Walt Disney Company, together with its subsidiaries and affiliates, is a leading diversified international family entertainment and media enterprise that includes three core business segments: Disney Entertainment, ESPN, and Disney Experiences. Our mission is to en...
Compliance Ranges Comparison
AEG
The Walt Disney Company
Benchmark & Cyber Underwriting Signals
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for AEG in 2026.
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for The Walt Disney Company in 2026.
Incident History - AEG (X = Date, Y = Severity)
AEG cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The Walt Disney Company (X = Date, Y = Severity)
The Walt Disney Company cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
AEG
The Walt Disney Company
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: *.*.