Comparison Overview
Kakao Entertainment

Kakao Entertainment
Pangyo, KR
Last Update: 29/09/2026
Kakao Entertainment is a leading entertainment company in Korea with a well-diversified portfolio offering everything from webtoons to films and dramas, talent management, and K-pop all under one roof. Using new imaginative ways to maximize the lifecycle and value of co...

Sony
1-7-1 Konan,, Tokyo, 108-0075, JP
Last Update: 07/10/2026
Sony’s purpose is simple. We aim to fill the world with emotion, through the power of creativity and technology. We want to be responsible for getting hearts racing, stirring ambition, and putting a smile on the faces of our customers. That challenge, combined with our ...
Compliance Ranges Comparison

Kakao Entertainment







Sony






Benchmark & Cyber Underwriting Signals
Incidents vs Entertainment Providers Industry Avg (This Year)
No incidents recorded for Kakao Entertainment in 2026.
Incidents vs Entertainment Providers Industry Avg (This Year)
Sony has 98.02% more incidents than the average of all companies with at least one recorded incident.
Incident History - Kakao Entertainment (X = Date, Y = Severity)
Kakao Entertainment cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sony (X = Date, Y = Severity)
Sony cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Kakao Entertainment

Sony
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.