Comparison Overview
Chick-fil-A Corporate Support Center

Chick-fil-A Corporate Support Center
5200 Buffington Road, Atlanta, 30349, US
Last Update: 06/09/2026
At its Atlanta headquarters, known as the Corporate Support Center, Chick-fil-A, Inc. offers full-time careers in various fields such as Digital Transformation & Technology, Financial Services & Accounting, Enterprise Analytics, Restaurant Development, Early Talent Prog...

Papa Johns
788 Circle 75 Pkwy SE, Atlanta, Georgia, US, 30339
Last Update: 17/09/2026
Papa Johns seeks people who have an entrepreneurial spirit and share our philosophy for success. Hands-on training, a clean and safe work environment, quality business practices, advancement opportunities and meaningful work combine to produce not only the best pizza, b...
Compliance Ranges Comparison

Chick-fil-A Corporate Support Center







Papa Johns






Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
Chick-fil-A Corporate Support Center has 146.31% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Papa Johns in 2026.
Incident History - Chick-fil-A Corporate Support Center (X = Date, Y = Severity)
Chick-fil-A Corporate Support Center cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Papa Johns (X = Date, Y = Severity)
Papa Johns cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Chick-fil-A Corporate Support Center

Papa Johns
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.