Comparison Overview
Barcel USA
Barcel USA
301 Northpoint Drive, Suite 100, Coppell, Texas, US, 75019
Last Update: 03/04/2026
Barcel USA is the snack division of Grupo Bimbo located in the United States. We are an exciting, young and fast-growing consumer packaged goods company headquartered in Coppell, Texas with a strong presence in the largest markets within United States territory. We manu...
US Foods
9399 W. Higgins Rd., Suite 500, Rosemont, IL, US, 60018
Last Update: 25/05/2026
US Foods is one of America’s great food companies and a leading foodservice distributor, partnering with approximately 300,000 restaurants and foodservice operators to help their businesses succeed. With 28,000 associates and more than 70 locations, US Foods provides ...
Compliance Ranges Comparison
Barcel USA
US Foods
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Barcel USA in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for US Foods in 2026.
Incident History - Barcel USA (X = Date, Y = Severity)
Barcel USA cyber incidents detection timeline including parent company and subsidiaries.
Incident History - US Foods (X = Date, Y = Severity)
US Foods cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Barcel USA
US Foods
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: *.*.