Comparison Overview
Chili's
Chili's
3000 Olympus Blvd, Dallas, Texas, US, 75019
Last Update: 01/04/2026
Chili's opened as a fun Dallas burger joint with a loyalty to happy hour and blue jeans. We prided ourselves on our humble beginnings, following a devotion to great food, warm hospitality and community spirit. Today, with restaurants all over the world, we continue to c...
Waffle House, Inc.
5986 Financial Dr NW, Norcross, 30071, US
Last Update: 01/04/2026
Waffle House has been serving Good Food Fast® since 1955. We started in one restaurant serving Avondale Estates, GA, and then grew into a national brand with more than 1,900 restaurants in 25 states providing career paths to 40,000 + employees. The love and devotion o...
Compliance Ranges Comparison
Chili's
Waffle House, Inc.
Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Chili's in 2026.
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Waffle House, Inc. in 2026.
Incident History - Chili's (X = Date, Y = Severity)
Chili's cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Waffle House, Inc. (X = Date, Y = Severity)
Waffle House, Inc. cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Chili's
Waffle House, Inc.
FAQ
Latest Global CVEs
Use after free in Aura in Google Chrome prior to 150.0.7871.128 allowed a local attacker to potentially exploit heap corruption via a malicious file. (Chromium security severity: High)
Use after free in Ozone in Google Chrome on Linux prior to 150.0.7871.128 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
Out of bounds read and write in V8 in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Use after free in Cast in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Use after free in Network in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)