Comparison Overview
RPSG (FMCG) - Guiltfree Industries Limited

RPSG (FMCG) - Guiltfree Industries Limited
2/4 Judges Court Road, Kolkata, 700027, IN
Last Update: 30/03/2026
RPSG FMCG Business has made strong initial inroads by creating a new segment of snacks in the Indian market, with its brand “Too Yumm!” In a short period the brand has established itself across India as a strong choice vis a vis of traditional fried. This was possible b...

PepsiCo
700 Anderson Hill Road, Purchase, 10577, US
Last Update: 22/04/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...
Compliance Ranges Comparison

RPSG (FMCG) - Guiltfree Industries Limited







PepsiCo






Benchmark & Cyber Underwriting Signals
Incidents vs Food and Beverage Services Industry Avg (This Year)
No incidents recorded for RPSG (FMCG) - Guiltfree Industries Limited in 2026.
Incidents vs Food and Beverage Services Industry Avg (This Year)
PepsiCo has 7.41% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - RPSG (FMCG) - Guiltfree Industries Limited (X = Date, Y = Severity)
RPSG (FMCG) - Guiltfree Industries Limited 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

RPSG (FMCG) - Guiltfree Industries Limited

PepsiCo
FAQ
Latest Global CVEs
An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command
The $_internalApplyOplogUpdate aggregation pipeline stage can be used to execute a document diff containing a malformed binary diff to return memory out-of-bounds or crash the server. $_internalApplyOplogUpdate can be executed by any authenticated user with access to the aggregate command.
An authorized user could trigger a server crash by running a query with a 2dsphere index on a field that stores a GeoJSON GeometryCollection containing a Polygon with a strict-winding CRS. Strict-winding polygons are intentionally unsupported for indexing, but the guard that rejects them does not inspect members of a GeometryCollection, allowing the unsafe path to be reached which ends with an ensuing null-pointer dereference.
The ldapQueryPassword parameter, when set through the runtime setParameter command, will log the new password to the mongod.log file in plain text.
An authenticated user can cause a MongoDB server to crash or return incorrect results by creating documents that interfere with internal metadata processing during query execution. This stems from insufficient separation between user-controlled document fields and internal metadata in certain execution paths.