Comparison Overview
Chick-fil-A Restaurants

Chick-fil-A Restaurants
5200 Buffington Rd, Atlanta, GA, US, 30349
Last Update: 04/04/2026
Chick-fil-A, Inc. is the third largest quick-service restaurant company in the United States, known for its freshly-prepared food, signature hospitality and unique franchise model. More than 200,000 Team Members are employed by independent Owner-Operators in more than 3...

Jersey Mike's Subs
2251 Landmark Place, Manasquan, NJ, US, 08736
Last Update: 19/09/2026
Jersey Mike’s, a fast-casual sub sandwich franchise with more than 3,100 locations open nationwide, believes that making a sub sandwich and making a difference can be one and the same. Jersey Mike’s offers A Sub Above®, serving authentic fresh sliced subs and authentic...
Compliance Ranges Comparison

Chick-fil-A Restaurants







Jersey Mike's Subs






Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Chick-fil-A Restaurants in 2026.
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Jersey Mike's Subs in 2026.
Incident History - Chick-fil-A Restaurants (X = Date, Y = Severity)
Chick-fil-A Restaurants cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Jersey Mike's Subs (X = Date, Y = Severity)
Jersey Mike's Subs cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Chick-fil-A Restaurants

Jersey Mike's Subs
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.