Comparison Overview
Neo Media World (no longer active)

Neo Media World (no longer active)
3 World Trade Center, New York, NY, 10007, US
Last Update: 04/03/2026
This page is no longer active. Please follow GroupM's page: https://www.linkedin.com/company/groupmworldwide/ -- Neo Media World is a digital-first global team with media expertise from brand to performance. Brands look to Neo as their competitive advantage to best eng...

Publicis Groupe
133, avenue des Champs-Elysées, Paris, 75008, FR
Last Update: 07/05/2026
Founded in 1926 by Marcel Bleustein-Blanchet, today Publicis Groupe is the largest communications group in the world and a leader in marketing, communication, and digital business transformation, led by Arthur Sadoun, the third CEO in its history. Publicis Groupe is p...
Compliance Ranges Comparison

Neo Media World (no longer active)







Publicis Groupe






Benchmark & Cyber Underwriting Signals
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Neo Media World (no longer active) in 2026.
Incidents vs Advertising Services Industry Avg (This Year)
No incidents recorded for Publicis Groupe in 2026.
Incident History - Neo Media World (no longer active) (X = Date, Y = Severity)
Neo Media World (no longer active) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Publicis Groupe (X = Date, Y = Severity)
Publicis Groupe cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Neo Media World (no longer active)

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