Comparison Overview
Seasons 52 Restaurant

Seasons 52 Restaurant
undefined, undefined, undefined, undefined, US
Last Update: 01/04/2026
The Best of Each Season. Straight to Your Table. Seasons 52 is a celebration of what’s good now. Seasonally inspired menus featuring ingredients at their peak of freshness. Rustic cooking techniques like brick oven roasting and open-fire grilling that bring out natura...

In-N-Out Burger
4199 Campus Drive, Irvine, 92612, US
Last Update: 01/04/2026
In-N-Out Burger was founded in 1948 by Harry and Esther Snyder in Baldwin Park, California, and remains privately owned and operated. Under the direction of the Snyder family, the company has opened restaurants throughout California, Nevada, Arizona, Utah, Texas, Orego...
Compliance Ranges Comparison

Seasons 52 Restaurant







In-N-Out Burger






Benchmark & Cyber Underwriting Signals
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for Seasons 52 Restaurant in 2026.
Incidents vs Restaurants Industry Avg (This Year)
No incidents recorded for In-N-Out Burger in 2026.
Incident History - Seasons 52 Restaurant (X = Date, Y = Severity)
Seasons 52 Restaurant cyber incidents detection timeline including parent company and subsidiaries.
Incident History - In-N-Out Burger (X = Date, Y = Severity)
In-N-Out Burger cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Seasons 52 Restaurant

In-N-Out Burger
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: *.*.