Comparison Overview
Funky Buddha Brewery

Funky Buddha Brewery
N/A
Last Update: 28/11/2025
Our 54,000 square-foot production brewery is located in the city of Oakland Park, in the heart of sunny South Florida. Opened in June, 2013, this facility is the first of its kind in Broward County and the largest brewery in South Florida. This unique facility also feat...

Greggs
GB
Last Update: 02/04/2026
Greggs is a leading food-on-the-go retailer with over 2,400 shops nationwide and serving over six million customers a week. We stand for great tasting, freshly prepared food that our customers can trust, at affordable prices and aim to become the customers’ favourite ...
Compliance Ranges Comparison

Funky Buddha Brewery







Greggs






Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Funky Buddha Brewery in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Greggs in 2026.
Incident History - Funky Buddha Brewery (X = Date, Y = Severity)
Funky Buddha Brewery cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Greggs (X = Date, Y = Severity)
Greggs cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Funky Buddha Brewery

Greggs
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: *.*.