Comparison Overview
Hobart Food Equipment and Service
Hobart Food Equipment and Service
701 S Ridge Ave, Troy, Ohio, 45373, US
Last Update: 13/11/2025
While running a business you constantly have a million things going on in your operation every day and any one of them can go wrong without notice. You’ve been around the block enough to know how to work-around many of them, but your mission critical foodservice equipm...
The ODP Corporation
Boca Raton, US
Last Update: 01/04/2026
The ODP Corporation (NASDAQ:ODP) is a leading provider of products and services through an integrated business-to-business (B2B) distribution platform and omnichannel presence, which includes world-class supply chain and distribution operations, dedicated sales professi...
Compliance Ranges Comparison
Hobart Food Equipment and Service
The ODP Corporation
Benchmark & Cyber Underwriting Signals
Incidents vs Retail Office Equipment Industry Avg (This Year)
No incidents recorded for Hobart Food Equipment and Service in 2026.
Incidents vs Retail Office Equipment Industry Avg (This Year)
No incidents recorded for The ODP Corporation in 2026.
Incident History - Hobart Food Equipment and Service (X = Date, Y = Severity)
Hobart Food Equipment and Service cyber incidents detection timeline including parent company and subsidiaries.
Incident History - The ODP Corporation (X = Date, Y = Severity)
The ODP Corporation cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Hobart Food Equipment and Service
The ODP Corporation
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: *.*.