Comparison Overview
Bonefish Grill

Bonefish Grill
undefined, undefined, undefined, undefined, US
Last Update: 17/03/2026
Since the first Bonefish Grill anchored in St. Petersburg, Florida in the year 2000, we’ve expanded our net nationwide to share our deep passion for fresh seafood. Our founders set out to create a truly unique, explorative, and memorable dining experience. At Bonefis...

LongHorn Steakhouse
US
Last Update: 05/09/2026
With over 500+ restaurants across the United States, LongHorn Steakhouse has a passion for steak done the right way. Our legendary food sets us apart, but it’s our people who bring LongHorn to life. We strive to create a place where team members feel valued, listened t...
Compliance Ranges Comparison

Bonefish Grill







LongHorn Steakhouse






Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Bonefish Grill in 2026.
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for LongHorn Steakhouse in 2026.
Incident History - Bonefish Grill (X = Date, Y = Severity)
Bonefish Grill cyber incidents detection timeline including parent company and subsidiaries.
Incident History - LongHorn Steakhouse (X = Date, Y = Severity)
LongHorn Steakhouse cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Bonefish Grill

LongHorn Steakhouse
FAQ
Latest Global CVEs
The web management service in affected RouterOS versions contains an integer underflow in its HTTP request body handling that is reachable before authentication. This can be leveraged by an unauthenticated network attacker to achieve arbitrary code execution as root, or to cause a denial of service, using a single crafted request.
Denuvo Anti-Tamper through 2026-03-04 allows bypass of a hypervisor presence check via CPUID interception (SimpleSvm.sys on AMD; hyperkd.sys and hyperhv.dll on Intel).
PeaZip before 11.3.0, in a non-default configuration, is vulnerable to OS command injection via a filename in an archive because "quotation character already used in the string" is mishandled.
Zilliz Attu before 3.0.0 has a Playground feature that does not require authentication for proxying arbitrary HTTP and HTTPS requests to URLs on the public internet.
The Playground feature of Zilliz Attu before 3.0.0 allows SSRF (proxying of requests to private IP addresses).