Comparison Overview
TGI Fridays

TGI Fridays
19111 North Dallas Parkway, Dallas, 75287, US
Last Update: 20/09/2026
In 1965, TGI Fridays opened its first location in New York City. Today, there are 380 plus restaurants in 30 plus countries offering high-quality, authentic American food and legendary drinks, bringing together all people from all places. The freeing and liberating spir...

Red Robin
6312 S. Fiddler's Green Circle, Suite 200 North, Greenwood Village, CO, US, 80111
Last Update: 17/09/2026
Since opening in 1969 in Seattle, Washington, Red Robin has welcomed Guests to our casual dining restaurants in the U.S. and Canada, connecting people around craveable food and fun in a relaxed, playful atmosphere. Our people are the foundation of our success. We aim t...
Compliance Ranges Comparison

TGI Fridays







Red Robin






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

TGI Fridays

Red Robin
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.