Comparison Overview

Bimo

VS

PepsiCo

Bimo

Last Update: 2025-03-15 (UTC)
Between 900 and 1000

Excellent

Blvd. Chefchaouni, Rue E Rte. 110, Ain Sebaa, Casablanca, 20250, Morocco ()212 0522 34 53 00, 212 0522 35 45 80 fax,

NAICS: 722
NAICS Definition:
Employees: 1,001-5,000
Subsidiaries: 0
12-month incidents
0
Known data breaches
0
Attack type number
0

PepsiCo

700 Anderson Hill Road, None, Purchase, New York, US, 10577
Last Update: 2025-09-07 (UTC)

Excellent

Between 900 and 1000

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. Together, we dare to make the world a better place. Our associates are the magic ingredient. Each of them plays an integral role in helping create deep connections between people and our products. Think about your last group celebration: Chances are, one of our iconic brands was by your side. At PepsiCo, youโ€™re invited to be a part of a global team of innovators who make, move, and sell these productsโ€”which are enjoyed by more than 1 billion people a day. A career at PepsiCo means working in a culture where everyoneโ€™s welcome. Here, you can dare to be yourself. No matter who you are or where youโ€™re from, you can influence the people around you and the world at large. By showing up, youโ€™ll have the opportunity to learn, develop and grow your skills for the future. Our supportive teams can fuel your professional goals to make a global impact on people and the planet. Join us. Dare for Better.

NAICS: 722
NAICS Definition: Food Services and Drinking Places
Employees: 147,898
Subsidiaries: 5
12-month incidents
0
Known data breaches
0
Attack type number
0

Compliance Badges Comparison

Security & Compliance Standards Overview

https://images.rankiteo.com/companyimages/bimo.jpeg
Bimo
โ€”
ISO 27001
Not verified
โ€”
SOC 2
Not verified
โ€”
GDPR
No public badge
โ€”
PCI DSS
No public badge
https://images.rankiteo.com/companyimages/pepsico.jpeg
PepsiCo
โ€”
ISO 27001
Not verified
โ€”
SOC 2
Not verified
โ€”
GDPR
No public badge
โ€”
PCI DSS
No public badge
Compliance Summary
Bimo
100%
Compliance Rate
0/4 Standards Verified
PepsiCo
0%
Compliance Rate
0/4 Standards Verified

Benchmark & Cyber Underwriting Signals

Incidents vs Food and Beverage Services Industry Average (This Year)

No incidents recorded for Bimo in 2025.

Incidents vs Food and Beverage Services Industry Average (This Year)

No incidents recorded for PepsiCo in 2025.

Incident History โ€” Bimo (X = Date, Y = Severity)

Bimo cyber incidents detection timeline including parent company and subsidiaries

Incident History โ€” PepsiCo (X = Date, Y = Severity)

PepsiCo cyber incidents detection timeline including parent company and subsidiaries

Notable Incidents

Last 3 Security & Risk Events by Company

https://images.rankiteo.com/companyimages/bimo.jpeg
Bimo
Incidents

No Incident

https://images.rankiteo.com/companyimages/pepsico.jpeg
PepsiCo
Incidents

No Incident

FAQ

Both Bimo company and PepsiCo company demonstrate a comparable AI risk posture, with strong governance and monitoring frameworks in place.

Historically, PepsiCo company has disclosed a higher number of cyber incidents compared to Bimo company.

In the current year, PepsiCo company and Bimo company have not reported any cyber incidents.

Neither PepsiCo company nor Bimo company has reported experiencing a ransomware attack publicly.

Neither PepsiCo company nor Bimo company has reported experiencing a data breach publicly.

Neither PepsiCo company nor Bimo company has reported experiencing targeted cyberattacks publicly.

Neither Bimo company nor PepsiCo company has reported experiencing or disclosing vulnerabilities publicly.

PepsiCo company has more subsidiaries worldwide compared to Bimo company.

PepsiCo company employs more people globally than Bimo company, reflecting its scale as a Food and Beverage Services.

Latest Global CVEs (Not Company-Specific)

Description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in The Wikimedia Foundation MediaWiki Cargo extension allows SQL Injection.This issue affects MediaWiki Cargo extension: 1.39, 1.43, 1.44.

Risk Information
cvss4
Base: 2.1
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:Y/R:U/V:C/RE:M/U:Amber
Description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in The Wikimedia Foundation MediaWiki QuizGame extension allows Stored XSS.This issue affects MediaWiki QuizGame extension: 1.39, 1.43, 1.44.

Risk Information
cvss4
Base: 2.0
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:U/V:C/RE:M/U:Amber
Description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in The Wikimedia Foundation MediaWiki PollNY extension allows Stored XSS.This issue affects MediaWiki PollNY extension: 1.39, 1.43, 1.44.

Risk Information
cvss4
Base: 2.0
Severity: HIGH
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:N/AU:N/R:U/V:C/RE:M/U:Amber
Description

Improper Neutralization of Input During Web Page Generation (XSS or 'Cross-site Scripting') vulnerability in The Wikimedia Foundation MediaWiki WebAuthn extension allows Stored XSS.This issue affects MediaWiki WebAuthn extension: 1.39, 1.43, 1.44.

Risk Information
cvss4
Base: 5.8
Severity: LOW
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:N/R:U/V:C/RE:L/U:Amber
Description

pyquokka is a framework for making data lakes work for time series. In versions 0.3.1 and prior, the FlightServer class directly uses pickle.loads() to deserialize action bodies received from Flight clients without any sanitization or validation in the do_action() method. The vulnerable code is located in pyquokka/flight.py at line 283 where arbitrary data from Flight clients is directly passed to pickle.loads(). When FlightServer is configured to listen on 0.0.0.0, this allows attackers across the entire network to perform arbitrary remote code execution by sending malicious pickled payloads through the set_configs action. Additional vulnerability points exist in the cache_garbage_collect, do_put, and do_get functions where pickle.loads is used to deserialize untrusted remote data.

Risk Information
cvss3
Base: 9.8
Severity: LOW
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H