Comparison Overview
NEVERHACK Estonia

NEVERHACK Estonia
Veskiposti 2, City Centre, Harju, 11313, EE
Last Update: 05/01/2026
NEVERHACK is a French group specialized in cybersecurity for over 40 years, and NEVERHACK Estonia (previously CYBERS) is proud part of it! Founded in 2021 and operating in 10 countries, the group now has over 1200 collaborators worldwide. Our ambition is to expand inte...

Palo Alto Networks
3000 Tannery Way, SANTA CLARA, California, US, 95054
Last Update: 30/05/2026
Palo Alto Networks, the global cybersecurity leader, is shaping the cloud-centric future with technology that is transforming the way people and organizations operate. Our mission is to be the cybersecurity partner of choice, protecting our digital way of life. We help ...
Compliance Ranges Comparison

NEVERHACK Estonia







Palo Alto Networks






Benchmark & Cyber Underwriting Signals
Incidents vs Computer and Network Security Industry Avg (This Year)
No incidents recorded for NEVERHACK Estonia in 2026.
Incidents vs Computer and Network Security Industry Avg (This Year)
Palo Alto Networks has 548.15% more incidents than the average of all companies with at least one recorded incident.
Incident History - NEVERHACK Estonia (X = Date, Y = Severity)
NEVERHACK Estonia cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Palo Alto Networks (X = Date, Y = Severity)
Palo Alto Networks cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

NEVERHACK Estonia

Palo Alto Networks
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.