Comparison Overview
Disneyland Resort

Disneyland Resort
undefined, Anaheim, undefined, undefined, US
Last Update: 07/03/2026
Walt Disney opened Disneyland Park on July 17, 1955, with hopes that it would become “a source of joy and inspiration to all the world.” Since then, the Disneyland Resort in Anaheim, Calif., has welcomed guests from around the world, expanding to become an approximately...

DIRECTV
2230 E Imperial Hwy, El Segundo, 90245, US
Last Update: 04/04/2026
At DIRECTV, we believe TV is meant to be enjoyed. Everything we do is focused on delivering an entertainment experience above and beyond expectations and industry standards and advocating for excellence on behalf of our customers. A shared passion for the joy of tel...
Compliance Ranges Comparison

Disneyland Resort







DIRECTV






Benchmark & Cyber Underwriting Signals
Incidents vs Entertainment Industry Avg (This Year)
No incidents recorded for Disneyland Resort in 2026.
Incidents vs Entertainment Industry Avg (This Year)
No incidents recorded for DIRECTV in 2026.
Incident History - Disneyland Resort (X = Date, Y = Severity)
Disneyland Resort cyber incidents detection timeline including parent company and subsidiaries.
Incident History - DIRECTV (X = Date, Y = Severity)
DIRECTV cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Disneyland Resort

DIRECTV
FAQ
Latest Global CVEs
FileBrowser Quantum is a free, self-hosted, web-based file manager. Versions prior to 1.3.2-stable, 1.4.0-beta and 1.4.1-beta are vulnerable to Path Traversal through the publicPatchHandler in backend/http/public.go which joins user-controlled fromPath and toPath body fields with the trusted d.share.Path BEFORE the downstream sanitizer runs. Because filepath.Join collapses .. segments during the join, the sanitizer in resourcePatchHandler never sees the traversal and the move/copy/rename operates on a path outside the shared directory. The same root-cause pattern was patched for the bulk DELETE endpoint as CVE-2026-44542 (GHSA-fwj3-42wh-8673), but the PATCH handler with the identical pattern was not updated. A public share link with AllowModify=true is sufficient to exploit this. Anyone holding such a link can move, copy, or rename arbitrary files within the share owner's source root. This issue has been fixed in versions 1.3.3-stable and 1.4.2-beta.
stable-diffusion.cpp is a pure C/C++ library for running diffusion model (Stable Diffusion, Flux, Wan, Qwen Image, Z-Image, and more) inference. In versions prior to master-584-0a7ae07, the pickle .ckpt parser in src/model.cpp contained a heap buffer overflow vulnerability in the GLOBAL opcode handler. The issue was caused by missing validation when searching for newline-delimited fields. A crafted .ckpt file without the expected newline could cause the parser to use -1 as a copy length, resulting in immediate heap corruption. The attack requires the victim or application to load a .ckpt file from an untrusted source, such as a downloaded model from a model sharing site. The issue has been resolved in version master-584-0a7ae07. If developers are unable to immediately update their applications they can work around this issue by following these instructions: do not load .ckpt checkpoint files from untrusted sources, and prefer trusted model sources and safer formats such as .safetensors where possible.
stable-diffusion.cpp is a pure C/C++ library for running diffusion model (Stable Diffusion, Flux, Wan, Qwen Image, Z-Image, and more) inference. In versions prior to master-584-0a7ae07, the pickle .ckpt parser in src/model.cpp contained a heap buffer overflow vulnerability in the BINUNICODE opcode handler. The issue was caused by sign confusion on the opcode length field. A crafted .ckpt file could trigger memcpy with a very large length derived from a negative signed value, causing immediate heap corruption. The issue has been resolved in version master-584-0a7ae07. If developers are unable to immediately update their applications they can work around this issue by only loading .ckpt checkpoint files from trusted sources and preferring trusted model sources and safer formats such as .safetensors where possible.
In OpenStack Nova before 33.0.2, the server create API does not strip certain hint data. The resulting instance has no Placement allocation.
The device has a webserver that exposes a REST API authenticated with a token on the management network. By exploiting an OS command injection vulnerability an authenticated attacker can send arbitrary commands to the device that are executed with administrative permissions by the underlying operating system.