Comparison Overview
Digital De Agostini

Digital De Agostini
Via Tito Speri, 8, Milan, Lombardy, 20154, IT
Last Update: 29/01/2026
Digital De Agostini is a De Agostini Editore business unit created in 2008 to develop business on television and digital platforms, through the creation of original properties that are consistent with the company's history and values. The brands built and managed within...

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

Digital De Agostini







iHeartMedia






Benchmark & Cyber Underwriting Signals
Incidents vs Broadcast Media Production and Distribution Industry Avg (This Year)
No incidents recorded for Digital De Agostini in 2026.
Incidents vs Broadcast Media Production and Distribution Industry Avg (This Year)
No incidents recorded for iHeartMedia in 2026.
Incident History - Digital De Agostini (X = Date, Y = Severity)
Digital De Agostini 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

Digital De Agostini

iHeartMedia
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.