Comparison Overview
FreshPoint, Inc.

FreshPoint, Inc.
1390 Enclave Pkwy, Houston, Texas, 77077, US
Last Update: 14/02/2026
FreshPoint is North America’s largest exclusively owned produce distributor. We have the line authority to hold our companies accountable to a high level of customer service. With unmatched fresh produce, knowledge and experience, FreshPoint provides today’s chefs with ...

Perfetti Van Melle
Stationsplein ZW 997, SCHIPHOL OOST, 1117 CE, NL
Last Update: 02/04/2026
Perfetti Van Melle is a privately owned company, producing and distributing candies and chewing gums in more than 150 countries worldwide. Employing over 17.000 people and operating 37 companies throughout the world, Perfetti Van Melle has a true global reach: it is p...
Compliance Ranges Comparison

FreshPoint, Inc.







Perfetti Van Melle






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

FreshPoint, Inc.

Perfetti Van Melle
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: *.*.