Comparison Overview
LongHorn Steakhouse
LongHorn Steakhouse
US
Last Update: 01/04/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...
Pizza Hut
7100 Corporate Dr, Plano, 75024, US
Last Update: 01/04/2026
Pizza Hut, a subsidiary of Yum! Brands, Inc. (NYSE: YUM), was founded in 1958 in Wichita, Kansas, and is a global leader in the pizza category with nearly 20,000 restaurants in more than 110 markets and territories. The brand has earned a reputation as a trailblazer in ...
Compliance Ranges Comparison
LongHorn Steakhouse
Pizza Hut
Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for LongHorn Steakhouse in 2026.
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Pizza Hut in 2026.
Incident History - LongHorn Steakhouse (X = Date, Y = Severity)
LongHorn Steakhouse cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Pizza Hut (X = Date, Y = Severity)
Pizza Hut cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
LongHorn Steakhouse
Pizza Hut
FAQ
Latest Global CVEs
Spinnaker is an open source, multi-cloud continuous delivery platform. Prior to versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4 on their respective release lines, Kustomize bake operations allow unsafe YAML tag processing in rosco manifests. This can lead to remote code execution on rosco pods when performing Kustomize bakes. This issue is fixed in versions 2026.1.1, 2026.0.3, 2025.4.4, and 2025.3.4.
- https://github.com/spinnaker/spinnaker/commit/2d75818b85cc4c35144d5e5ed45e7340fcab5dfe
- https://github.com/spinnaker/spinnaker/commit/bbc30c9b9034a056e95f012fa1b34e9fd703cae7
- https://github.com/spinnaker/spinnaker/commit/de5a7a05af35aee19eb71d289cd0b77f67509009
- https://github.com/spinnaker/spinnaker/commit/df32d568e82519d9f3896fc9007baba0077c87fd
- https://github.com/spinnaker/spinnaker/commit/f5cec213f8cf207843ed5a6929395960a1ca094f
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.3.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2025.4.4
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.0.3
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.1.1
- https://github.com/spinnaker/spinnaker/releases/tag/rosco-2026.2.0
- https://github.com/spinnaker/spinnaker/security/advisories/GHSA-p68j-q7hf-3qcp
Multiple connections to the backend using the same charging station ID are allowed, which could allow an attacker to deploy multiple instances of malicious OCPP clients to overwhelm the backend.
Previously, there was no throttling on repeated authentication attempts to the charging station backend, which could allow an attacker to execute a denial-of-service attack.
The charging station websocket endpoint accepts connections without proper authentication, which could lead to privilege escalation.
vulnerability in Drupal Commerce guest registration allows . This issue affects Commerce guest registration versions: *.*.