Comparison Overview
Paramount Television Studios

Paramount Television Studios
5555 Melrose Ave, None, Los Angeles, California, US, 90038
Last Update: 17/02/2026
Paramount Television Studios is a leading studio, developing and financing a wide range of cutting-edge and entertaining television content across all media platforms for distribution worldwide. The studio’s robust slate includes THE OFFER (Paramount+), GREASE: RISE OF ...

Sony
1-7-1 Konan,, Tokyo, 108-0075, JP
Last Update: 01/04/2026
Sony’s purpose is simple. We aim to fill the world with emotion, through the power of creativity and technology. We want to be responsible for getting hearts racing, stirring ambition, and putting a smile on the faces of our customers. That challenge, combined with our ...
Compliance Ranges Comparison

Paramount Television Studios







Sony






Benchmark & Cyber Underwriting Signals
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for Paramount Television Studios in 2026.
Incidents vs Entertainment Providers Industry Avg (This Year)
Sony has 7.41% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Paramount Television Studios (X = Date, Y = Severity)
Paramount Television Studios cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sony (X = Date, Y = Severity)
Sony cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Paramount Television Studios

Sony
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.