Comparison Overview
Walt Disney Imagineering
Walt Disney Imagineering
undefined, Glendale, California, 91201, US
Last Update: 07/03/2026
Founded by Walt Disney himself in 1952, Walt Disney Imagineering is the creative force behind the eye-opening, mind-blowing and heartfelt Disney experiences that connect and inspire across generations and borders. More than 70 years later, our experiences continue to se...
Live Nation Entertainment
9348 Civic Center Dr, Beverly Hills, 90210, US
Last Update: 31/03/2026
Recognized three years in a row by Great Place to Work® and named one of People Magazine’s Top 50 Companies that Care, Live Nation Entertainment is the global leader in live events and ticketing. With business operations and corporate functions across major divisions in...
Compliance Ranges Comparison
Walt Disney Imagineering
Live Nation Entertainment
Benchmark & Cyber Underwriting Signals
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for Walt Disney Imagineering in 2026.
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for Live Nation Entertainment in 2026.
Incident History - Walt Disney Imagineering (X = Date, Y = Severity)
Walt Disney Imagineering cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Live Nation Entertainment (X = Date, Y = Severity)
Live Nation Entertainment cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Walt Disney Imagineering
Live Nation Entertainment
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: *.*.