Comparison Overview
PepsiCo

PepsiCo
700 Anderson Hill Road, Purchase, 10577, US
Last Update: 14/09/2026
PepsiCo is a playground for curious people. We invite thinkers, doers, and changemakers to champion innovation, take calculated risks, and challenge the status quo. From executives to team members on the front lines, we’re excited about the future. We take chances. Toge...

Sysco
1390 Enclave Parkway, Houston, 77079, US
Last Update: 15/09/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

PepsiCo







Sysco






Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
PepsiCo has 6.95% more incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Food and Beverage Services Industry Avg (This Year)
Sysco has 194.12% more incidents than the average of all companies with at least one recorded incident.
Incident History - PepsiCo (X = Date, Y = Severity)
PepsiCo 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

PepsiCo

Sysco
FAQ
Latest Global CVEs
A vulnerability was detected in mathurvishal CloudClassroom-PHP-Project up to 5dadec098bfbbf3300d60c3494db3fb95b66e7be. This impacts an unknown function of the file viewresult.php. Performing a manipulation of the argument seno results in sql injection. Remote exploitation of the attack is possible. The exploit is now public and may be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The vendor was contacted early about this disclosure but did not respond in any way.
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Kibana can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)
Uncontrolled Resource Consumption (CWE-400) in Elasticsearch can lead denial of service via Excessive Allocation (CAPEC-130)