Comparison Overview
Jack in the Box

Jack in the Box
9357 Spectrum Center Blvd, San Diego, California, US, 92123
Last Update: 05/09/2026
Jack in the Box has always been the place for those who live outside the box. Where you can try new things and order what you want when you want it. Now, let’s get to the facts! Did you know Jack in the Box was founded on February 21, 1951, by a businessman named Robert...

Domino's
30 Frank Lloyd Wright Dr, Ann Arbor, 48106, US
Last Update: 11/09/2026
Domino’s is a purpose-inspired, performance-driven company powered by exceptional people who are committed to feeding the power of possible—one pizza at a time. Founded in 1960 with a single store in Ypsilanti, Michigan, Domino’s has grown into one of the most recogniz...
Compliance Ranges Comparison

Jack in the Box







Domino's






Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Jack in the Box in 2026.
Incidents vs Restaurants Industry Avg (This Year)
Domino's has 1.96% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Jack in the Box (X = Date, Y = Severity)
Jack in the Box cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Domino's (X = Date, Y = Severity)
Domino's cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Jack in the Box

Domino's
FAQ
Latest Global CVEs
Exim before 4.100.1 allows SMTP smuggling in which the received message does not match any sent message, and instead depends on crafted data sent after a rejection during DATA processing.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, allows attackers to read certain uninitialized data from stack memory.
Exim before 4.100.1, when certain non-default TLS settings are used with GnuTLS, has a use-after-free.
Exim before 4.100.1, when Proxy-Protocol is used with an attacker-controlled proxy, has an out-of-bounds write.
Mistral Vibe before 2.25.5 contains a remote code execution vulnerability in the worktree creation process that executes git hooks before trust validation. Attackers can supply a repository with a crafted post-checkout hook that executes arbitrary shell commands with the privileges of the user running Vibe.
- https://github.com/mistralai/mistral-vibe
- https://github.com/mistralai/mistral-vibe/blob/19b5b74faa78d0816b8d4d4c7d7543fc3520678c/vibe/core/git/repo.py#L411-L431
- https://github.com/mistralai/mistral-vibe/commit/c069ffa1e12fb5f2487b489217c40ab97721d553
- https://github.com/mistralai/mistral-vibe/issues/996
- https://github.com/mistralai/mistral-vibe/releases/tag/v2.25.5
- https://www.vulncheck.com/advisories/mistral-vibe-before-2.25.5-remote-code-execution-via-git-post-checkout