Comparison Overview
Amigos

Amigos
N/A
Last Update: 24/04/2026

Food Lion
2011 Executive Dr, Salisbury, 28147, US
Last Update: 01/04/2026
Food Lion, based in Salisbury, N.C., and its 82,000 associates have a longstanding history of serving its customers and communities through 10 Southeastern and Mid-Atlantic states. Since 1957, we have been connected to the towns and cities we serve by providing an easy ...
Compliance Ranges Comparison

Amigos







Food Lion






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Amigos in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Food Lion in 2026.
Incident History - Amigos (X = Date, Y = Severity)
Amigos cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Food Lion (X = Date, Y = Severity)
Food Lion cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Amigos

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