Comparison Overview
KFC

KFC
KFC Global Headquarters , Dallas, TX, US, 75024
Last Update: 05/09/2026
We’re KFC. The iconic, brand making world-famous finger lickin’ good fried chicken since 1952. Our unrivaled people and culture are the true heart and soul of our brand. It’s where our people promise comes to life every day. Where our employees can be their best selves,...

Panda Restaurant Group
1683 Walnut Grove Ave, Rosemead, 91770, US
Last Update: 07/09/2026
Panda Restaurant Group is the global leader in Asian dining and includes Panda Express, Panda Inn, and more. Founded in 1973 by Andrew and Peggy Cherng, we are a family-owned business with more than 2,600 restaurants worldwide. Our mission is to deliver exceptional Asia...
Compliance Ranges Comparison

KFC







Panda Restaurant Group






Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
KFC has 51.92% fewer 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 Panda Restaurant Group in 2026.
Incident History - KFC (X = Date, Y = Severity)
KFC cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Panda Restaurant Group (X = Date, Y = Severity)
Panda Restaurant Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

KFC

Panda Restaurant Group
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