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...

Krispy Kreme
2116 Hawkins St, Charlotte, North Carolina, US, 28203
Last Update: 14/09/2026
Headquartered in Charlotte, N.C., Krispy Kreme is one of the most beloved and well-known sweet treat brands in the world. Our iconic Original Glazed® doughnut is universally recognized for its hot-off-the-line, melt-in-your-mouth experience. Krispy Kreme operates in mor...
Compliance Ranges Comparison

PepsiCo







Krispy Kreme






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)
Krispy Kreme has 1.96% fewer 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 - Krispy Kreme (X = Date, Y = Severity)
Krispy Kreme cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

PepsiCo

Krispy Kreme
FAQ
Latest Global CVEs
Omni C20 lacks proper certificate validation which could allow an attacker to perform a man-in-the-middle attack which could allow them to execute arbitrary code.
Omni C20 uses hard-coded credentials that could allow an attacker to monitor log files to obtain credentials to access information like mapping data.
The affected products are vulnerable to command injection attack that could allow an unauthenticated attacker to execute system commands during the pairing process.
The Botslab G980H dash camera firmware contains an authentication vulnerability in the root account exposed through the device's UART interface. The affected account does not require a password before granting access to a privileged system interface, and the interface also displays the device's WiFi password during startup. An unauthenticated attacker with physical access to the device could connect to the UART interface, obtain root privileges, and recover the WiFi password.
The Botslab G980H dash camera firmware generates the default WiFi password using predictable device information, portions of which are advertised by the product. An unauthenticated attacker within WiFi range could potentially determine the remaining password characters through limited guessing and gain unauthorized access to the device network.