Comparison Overview
Jimmy John's

Jimmy John's
3 Glenlake Pkwy NE, Sandy Springs, Georgia, US, 30328
Last Update: 02/04/2026
THE SANDWICH OF SANDWICHES℠ At Jimmy John's, we don't make sandwiches. We make The Sandwich of Sandwiches℠. We use fresh vegetables because we don't hate salads, we just feel bad for them. We hand-slice our provolone cheese and meats in-house every day, because packag...

Popeyes Louisiana Kitchen
5707 Blue Lagoon Dr, Miami, Florida, US, 33126
Last Update: 02/04/2026
Founded in New Orleans in 1972, POPEYES® has more than 45 years of history and culinary tradition. Popeyes distinguishes itself with a unique New Orleans-style menu featuring spicy chicken, chicken tenders, fried shrimp, and other regional items. The chain's passion for...
Compliance Ranges Comparison

Jimmy John's







Popeyes Louisiana Kitchen






Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Jimmy John's in 2026.
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Popeyes Louisiana Kitchen in 2026.
Incident History - Jimmy John's (X = Date, Y = Severity)
Jimmy John's cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Popeyes Louisiana Kitchen (X = Date, Y = Severity)
Popeyes Louisiana Kitchen cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Jimmy John's

Popeyes Louisiana Kitchen
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.