Comparison Overview
TGI Fridays

TGI Fridays
19111 North Dallas Parkway, Dallas, 75287, US
Last Update: 01/04/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...

In-N-Out Burger
4199 Campus Drive, Irvine, 92612, US
Last Update: 01/04/2026
In-N-Out Burger was founded in 1948 by Harry and Esther Snyder in Baldwin Park, California, and remains privately owned and operated. Under the direction of the Snyder family, the company has opened restaurants throughout California, Nevada, Arizona, Utah, Texas, Orego...
Compliance Ranges Comparison

TGI Fridays







In-N-Out Burger






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 In-N-Out Burger in 2026.
Incident History - TGI Fridays (X = Date, Y = Severity)
TGI Fridays cyber incidents detection timeline including parent company and subsidiaries.
Incident History - In-N-Out Burger (X = Date, Y = Severity)
In-N-Out Burger cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

TGI Fridays

In-N-Out Burger
FAQ
Latest Global CVEs
PlaywrightCapture stored capture-specific configuration and runtime data as mutable class-level variables rather than instance-level variables. Consequently, multiple Capture objects running within the same Python process could share state, including HTTP headers, cookies, browser storage, HTTP credentials, proxy configuration, user-agent settings, geolocation information, and captured request data. In a multi-user or concurrent deployment, information supplied during one capture could therefore persist and be reused by a subsequent or parallel capture. This could result in the disclosure of authentication cookies, credentials, browser storage, or captured request data belonging to another user. It could also cause requests to be performed with another capture's authentication context, headers, or proxy configuration, potentially enabling unauthorized access to remote resources or interference with other capture operations. The vulnerability is resolved by initializing all capture-specific settings and request data as instance variables in the Capture constructor, ensuring that state is isolated between capture operations.
Anubis is a Web AI Firewall Utility that challenges users' connections in order to protect upstream resources from scraper bots. From 1.22.0 until 1.26.0-pre1, lib/policy/checker.go PathChecker.Check() trusted the client-controlled X-Original-URI header before matching r.URL.Path, allowing an HTTP client to match default data/common/keep-internet-working.yaml ALLOW rules such as ^/\.well-known/.*$ and bypass the Anubis challenge. This issue is fixed in version 1.26.0-pre1.
Wekan is open source kanban built with Meteor. Prior to 9.46, header-login with HEADER_LOGIN_TRUSTED_IPS uses getRequestIp() in server/lib/headerLoginAuth.js to trust the client-supplied X-Forwarded-For header before the real socket address, allowing an unauthenticated attacker to send HEADER_LOGIN_ID for any username and receive a meteor_login_token session, including for admin. This issue is fixed in version 9.46.
MaaAssistantArknights is a one-click tool for daily Arknights tasks. In the current dev-v2 workflow, .github/workflows/release-preparation.yml inlined attacker-controlled github.event.pull_request.title into a run: shell command during the pull_request opened, reopened, and ready_for_review events, so a non-draft fork PR whose title starts with Release v could execute shell commands on the ubuntu-latest runner during the generate-changelog job. This vulnerability is fixed by commit cafc3946059e6337d2089d4fec8b6885ba17c332.
Qinglong is a timed task management platform supporting Python3, JavaScript, Shell, and Typescript. Prior to 2.20.1, the init guard middleware in back/loaders/express.ts checks /api/user/init but not /open/user/init, while rewrite('/open/*', '/api/$1') rewrites the whitelisted /open/* path after JWT authentication and the guard have passed; an unauthenticated attacker can send PUT /open/user/init to reset administrator credentials on an initialized instance. This issue is fixed in 2.20.1.