Comparison Overview
Chipotle Mexican Grill

Chipotle Mexican Grill
610 Newport Center Dr, Newport Beach, California, US, 92660
Last Update: 03/07/2026
Chipotle Mexican Grill, Inc. (NYSE: CMG) is cultivating a better world by serving responsibly sourced, classically-cooked, real food with wholesome ingredients without artificial colors, flavors or preservatives. Chipotle has over 3,800 restaurants in the United States,...

Papa Johns
788 Circle 75 Pkwy SE, Atlanta, Georgia, US, 30339
Last Update: 01/04/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

Chipotle Mexican Grill







Papa Johns






Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Chipotle Mexican Grill in 2026.
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Papa Johns in 2026.
Incident History - Chipotle Mexican Grill (X = Date, Y = Severity)
Chipotle Mexican Grill 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

Chipotle Mexican Grill

Papa Johns
FAQ
Latest Global CVEs
In OpenStack Ironic before 38.0.1, the autodetect deploy interface may fail to run cleaning immediately after enrollment with, or changing to, the autodetect deploy interface.
A flaw was found in Red Hat Quay. A user with FEATURE_BUILD_SUPPORT enabled and repository write access can exploit a Server-Side Request Forgery (SSRF) vulnerability within the build API. This allows the user to provide a malicious URL, causing the Quay builder to make requests to internal network addresses. Such an action could lead to the disclosure of sensitive internal information.
A flaw was found in Red Hat Quay's exported logs feature. An unauthenticated attacker with a valid file ID could download exported action logs without proper authorization. While file IDs are complex, they can be intercepted from plaintext email or webhook callbacks. This vulnerability leads to information disclosure, potentially exposing sensitive data such as usernames, email addresses, IP addresses, and action-specific metadata.
A flaw was found in Red Hat Quay's Stripe billing webhook handler. This vulnerability allows an unauthenticated attacker to forge billing events by sending crafted JSON requests to the `/webhooks/stripe` endpoint without validating the Stripe-Signature header. Successful exploitation can lead to the unauthorized resetting of a namespace's build quota to its maximum and trigger unsolicited billing emails to namespace administrators.
A flaw was found in Red Hat Quay. When the SECURITY_SCANNER_V4_PSK (pre-shared key) is not set, a remote unauthenticated attacker can send POST requests to the security scanner notification endpoint. This allows the attacker to flood the notification queue and inject path traversal characters into Clair API URL paths. The primary consequence is worker resource exhaustion and blind path manipulation on the configured Clair host, potentially leading to a denial of service.