Comparison Overview
The Wonderful Company
The Wonderful Company
11444 W Olympic Blvd, Los Angeles, California, US, 90064
Last Update: 03/04/2026
Headquartered in Los Angeles, The Wonderful Company is a privately held $6 billion company dedicated to harvesting health around the world through its iconic consumer brands. The company’s 10,000 employees worldwide are committed to bringing consumers everywhere the fre...
Greencore
Greencore Group plc, Barlborough, S43 4XA, GB
Last Update: 01/06/2026
Greencore is the UK’s leading convenience food manufacturer. We bring industry-leading innovation to create high-quality, fresh and convenient food to customers and consumers. We supply all major UK supermarkets, convenience and travel retail outlets, discounters, cof...
Compliance Ranges Comparison
The Wonderful Company
Greencore
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for The Wonderful Company in 2026.
Incidents vs Food and Beverage Manufacturing Industry Avg (This Year)
No incidents recorded for Greencore in 2026.
Incident History - The Wonderful Company (X = Date, Y = Severity)
The Wonderful Company cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Greencore (X = Date, Y = Severity)
Greencore cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
The Wonderful Company
Greencore
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: *.*.