Comparison Overview
VIACOM BRASIL

VIACOM BRASIL
Rua Renato Paes de Barros, 1017, São Paulo, 04530-001, BR
Last Update: 28/01/2026
A Viacom International Media Networks (VIMN) Américas, dona da Viacom Brasil, é proprietária e opera um portfólio de diversas marcas de entretenimento que inclui MTV, Nickelodeon, Nick Jr., Noggin, Comedy Central, Porta dos Fundos, Telefe, Paramount Channel, Paramount P...

Cinemark
3900 Dallas Parkway, Plano, TX, US, 75093
Last Update: 30/03/2026
Headquartered in Plano, TX, Cinemark Holdings, Inc. provides premium out-of-home entertainment experiences as one of the largest and most influential theatrical exhibition companies in the world with 497 theatres and 5,644 screens in the U.S. and Latin America as of Sep...
Compliance Ranges Comparison

VIACOM BRASIL







Cinemark






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

VIACOM BRASIL

Cinemark
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: *.*.