Comparison Overview
Green Field Farms Co-op
Green Field Farms Co-op
6464 Fredericksburg Rd, None, Wooster, Ohio, US, 44691
Last Update: 29/03/2026
Green Field Farms firmly believes in continuing our old-world tradition of providing healthy, nourishing food, for you and your family. We are a farmer owned co-op that bridges the gap between our farms and your table with products that go Beyond Organic. We are your so...
HMSHost
US
Last Update: 01/04/2026
HMSHost is recognized by the industry as the leader in travel dining with awards such as Restaurateur with the Highest Regard for Customer Service and Best Brand Restaurateur for Shake Shack by Airport Experience News. USA Today 10Best Readers’ Choice Travel Awards gave...
Compliance Ranges Comparison
Green Field Farms Co-op
HMSHost
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Green Field Farms Co-op in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for HMSHost in 2026.
Incident History - Green Field Farms Co-op (X = Date, Y = Severity)
Green Field Farms Co-op cyber incidents detection timeline including parent company and subsidiaries.
Incident History - HMSHost (X = Date, Y = Severity)
HMSHost cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Green Field Farms Co-op
HMSHost
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: *.*.