Comparison Overview
Hallmark Media

Hallmark Media
Studio City, California, US, 91604
Last Update: 21/02/2026
Hallmark Media is entertainment’s leading destination for feel-good movies & series. We operate three cable networks - Hallmark Channel, Hallmark Mystery, and Hallmark Family - as well as Hallmark +, a subscription streaming service. Collectively, we feature an ambitiou...

Universal Music Group
2220 Colorado Avenue, Santa Monica, 90401, US
Last Update: 14/09/2026
Universal Music Group (UMG) is the world leader in music-based entertainment, with a broad array of businesses engaged in recorded music, music publishing, merchandising and audiovisual content in more than 60 countries. Featuring the most comprehensive catalog of recor...
Compliance Ranges Comparison

Hallmark Media







Universal Music Group






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

Hallmark Media

Universal Music Group
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.