Comparison Overview
Innovative Scientific Solutions, Inc

Innovative Scientific Solutions, Inc
7610 McEwen Road, Dayton, 45459, US
Last Update: 23/04/2026
Innovative Scientific Solutions Incorporated is an engineering research and development company providing innovative measurement and instrumentation solutions in the areas of Fluid Dynamics, Aerodynamics, Combustion Analysis, and Pressure/Force quantification. ISSI sup...

BAE Systems
BAE Systems, London, SW1Y 5AD, GB
Last Update: 01/04/2026
At BAE Systems, we help our customers to stay a step ahead when protecting people and national security, critical infrastructure and vital information. We provide some of the world’s most advanced, technology-led defence, aerospace and security solutions and employ a sk...
Compliance Ranges Comparison

Innovative Scientific Solutions, Inc







BAE Systems






Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
Innovative Scientific Solutions, Inc has 55.16% fewer incidents than the average of same-industry companies with at least one recorded incident.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for BAE Systems in 2026.
Incident History - Innovative Scientific Solutions, Inc (X = Date, Y = Severity)
Innovative Scientific Solutions, Inc cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BAE Systems (X = Date, Y = Severity)
BAE Systems cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Innovative Scientific Solutions, Inc

BAE Systems
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.