Comparison Overview
Zee Media Corporation Limited
Zee Media Corporation Limited
FC-19, Sector 16-A,, Noida, Uttar Pradesh, 201301, IN
Last Update: 25/03/2026
Zee Media network is one network that began early, grew steadily, adapted along, sustained all weathers and today stands as one of India’s largest, widest and most diverse-platform news network. Zee Media Corporation Limited has interests in Global, National and Regiona...
iHeartMedia
125 W 55th St., New York, NY, US, 10019
Last Update: 01/04/2026
iHeartMedia, Inc. [Nasdaq: IHRT] is the leading audio media company in America, with 90% of Americans listening to iHeart broadcast radio in every month. iHeart’s broadcast radio assets alone have a larger audience in the U.S. than any other media outlet; twice the size...
Compliance Ranges Comparison
Zee Media Corporation Limited
iHeartMedia
Benchmark & Cyber Underwriting Signals
Incidents vs Broadcast Media Production and Distribution Industry Avg (This Year)
No incidents recorded for Zee Media Corporation Limited in 2026.
Incidents vs Broadcast Media Production and Distribution Industry Avg (This Year)
No incidents recorded for iHeartMedia in 2026.
Incident History - Zee Media Corporation Limited (X = Date, Y = Severity)
Zee Media Corporation Limited cyber incidents detection timeline including parent company and subsidiaries.
Incident History - iHeartMedia (X = Date, Y = Severity)
iHeartMedia cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Zee Media Corporation Limited
iHeartMedia
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: *.*.