Comparison Overview
Lancer Hospitality Group

Lancer Hospitality Group
101 N Tryon St Suite 525, Charlotte, North Carolina, 28202, US
Last Update: 09/12/2025
Lancer Hospitality is a Minnesota-based hospitality company with a record of experience since 1976. Our services include campus dining, K-12 lunch programs, corporate dining, restaurant management, award-winning catering, and large-scale food service and retail operati...

Delaware North
250 Delaware Ave, Buffalo, 14202, US
Last Update: 08/06/2026
Delaware North is a global leader in the hospitality and entertainment industry. The company annually serves more than a half-billion guests across three continents, including at high-profile sports venues, airports, national and state parks, restaurants, resorts, hotel...
Compliance Ranges Comparison

Lancer Hospitality Group







Delaware North






Benchmark & Cyber Underwriting Signals
Incidents vs Hospitality Industry Avg (This Year)
No incidents recorded for Lancer Hospitality Group in 2026.
Incidents vs Hospitality Industry Avg (This Year)
Delaware North has 85.19% more incidents than the average of all companies with at least one recorded incident.
Incident History - Lancer Hospitality Group (X = Date, Y = Severity)
Lancer Hospitality Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Delaware North (X = Date, Y = Severity)
Delaware North cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Lancer Hospitality Group

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