Comparison Overview
Tubi

Tubi
315 Montgomery St., San Francisco, CA, 94104, US
Last Update: 26/03/2026
Tubi is the most watched free TV and movie streaming service in the U.S., dedicated to providing all people access to all the world's stories. As a leading ad-supported video-on-demand service, the company engages diverse audiences through a personalized experience and ...

Topgolf
8750 N. Central Expressway, Dallas, 75231, US
Last Update: 13/09/2026
Topgolf is the ultimate instigator of play. Thanks to our 100+ venues around the globe, which are powered by industry-leading Toptracer technology, we're leading the charge of modern golf. We offer a variety of tech-driven games, a top-tier food and drink menu, space to...
Compliance Ranges Comparison

Tubi







Topgolf






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

Tubi

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