Comparison Overview
Red Robin

Red Robin
6312 S. Fiddler's Green Circle, Suite 200 North, Greenwood Village, CO, US, 80111
Last Update: 17/09/2026
Since opening in 1969 in Seattle, Washington, Red Robin has welcomed Guests to our casual dining restaurants in the U.S. and Canada, connecting people around craveable food and fun in a relaxed, playful atmosphere. Our people are the foundation of our success. We aim t...

P.F. Chang's
8377 E Hartford Dr, #200, Scottsdale, Arizona, US, 85255
Last Update: 05/09/2026
P.F. Chang’s is a restaurant concept that honors the 2,000-year-old Asian tradition of wok cooking and believes in making food from scratch every day in every restaurant. Since inception, P.F. Chang’s chefs hand-roll dim sum, hand chop and slice all vegetables and meat...
Compliance Ranges Comparison

Red Robin







P.F. Chang's






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

Red Robin

P.F. Chang's
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)