Comparison Overview
IHOP

IHOP
undefined, Los Angeles, undefined, undefined, US
Last Update: 27/02/2026
67 years – that is a long time to smile. But at IHOP, we have been smiling and serving joy one plate at a time ever since Al and Jerry Lapin opened the first International House of Pancakes in Toluca Lake, California in 1958. It is even more important today, amid our ch...

Domino's
30 Frank Lloyd Wright Dr, Ann Arbor, 48106, US
Last Update: 07/10/2026
Domino’s is a purpose-inspired, performance-driven company powered by exceptional people who are committed to feeding the power of possible—one pizza at a time. Founded in 1960 with a single store in Ypsilanti, Michigan, Domino’s has grown into one of the most recogniz...
Compliance Ranges Comparison

IHOP







Domino's






Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for IHOP in 2026.
Incidents vs Restaurants Industry Avg (This Year)
Domino's has 0.99% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - IHOP (X = Date, Y = Severity)
IHOP cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Domino's (X = Date, Y = Severity)
Domino's cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

IHOP

Domino's
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.