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: 05/09/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
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.