Comparison Overview
Pepsi Bottling Ventures
Pepsi Bottling Ventures
4141 Parklake Ave, Raleigh, 27612, US
Last Update: 28/03/2026
Who We Are We are jointly owned by Suntory and PepsiCo. Suntory is a family-owned business founded in Japan more than 125 years ago that is known globally for their beverages and innovative spirit. PepsiCo has a 125-year plus legacy as a global leader in convenient food...
Sysco
1390 Enclave Parkway, Houston, 77079, US
Last Update: 28/06/2026
Sysco is the global leader in selling, marketing and distributing food and related products to customers who prepare meals away from home. This includes restaurants, healthcare and educational facilities, lodging establishments, entertainment venues, and more. Sysco ope...
Compliance Ranges Comparison
Pepsi Bottling Ventures
Sysco
Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for Pepsi Bottling Ventures in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
Sysco has 5.66% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Pepsi Bottling Ventures (X = Date, Y = Severity)
Pepsi Bottling Ventures cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Sysco (X = Date, Y = Severity)
Sysco cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Pepsi Bottling Ventures
Sysco
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: *.*.