Comparison Overview
Naval Surface Warfare Center (NSWC)

Naval Surface Warfare Center (NSWC)
Washington Navy Yard, Washington, DC, US, 20374
Last Update: 02/04/2026
The NAVSEA Warfare Centers (NSWC / NUWC) - part of the Naval Sea Systems Command - deliver seapower to the U.S. Navy. We are the Navy's trusted partner for identifying & providing innovative, cost-effective technical solutions to America's warfighters. Our 16,000 + sc...

Leidos
1750 Presidents St, Reston, 20190, US
Last Update: 05/04/2026
Leidos is a Fortune 500® innovation company rapidly addressing the world’s most vexing challenges in national security and health. The company's global workforce of 48,000 collaborates to create smarter technology solutions for customers in heavily regulated industries....
Compliance Ranges Comparison

Naval Surface Warfare Center (NSWC)







Leidos






Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for Naval Surface Warfare Center (NSWC) in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for Leidos in 2026.
Incident History - Naval Surface Warfare Center (NSWC) (X = Date, Y = Severity)
Naval Surface Warfare Center (NSWC) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Leidos (X = Date, Y = Severity)
Leidos cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Naval Surface Warfare Center (NSWC)

Leidos
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.