Comparison Overview
Air Force Research Laboratory

Air Force Research Laboratory
1864 4th Street, Wright-Patterson AFB, OH, US, 45433-7132
Last Update: 13/03/2026
WHAT WE DO We lead the discovery, development and delivery of warfighting technologies for our air, space and cyberspace forces. Through unparalleled research, tomorrow’s technology and strategic partnerships, we give our warfighters unmatched advantage in the field. Ba...

US Navy
1200 Navy Pentagon, Washington, 20350, US
Last Update: 02/04/2026
The United States is a maritime nation, and the U.S. Navy protects America at sea. Alongside our allies and partners, we defend freedom, preserve economic prosperity, and keep the seas open and free. Our nation is engaged in long-term competition. To defend American int...
Compliance Ranges Comparison

Air Force Research Laboratory







US Navy






Benchmark & Cyber Underwriting Signals
Incidents vs Armed Forces Industry Avg (This Year)
No incidents recorded for Air Force Research Laboratory in 2026.
Incidents vs Armed Forces Industry Avg (This Year)
No incidents recorded for US Navy in 2026.
Incident History - Air Force Research Laboratory (X = Date, Y = Severity)
Air Force Research Laboratory cyber incidents detection timeline including parent company and subsidiaries.
Incident History - US Navy (X = Date, Y = Severity)
US Navy cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Air Force Research Laboratory

US Navy
FAQ
Latest Global CVEs
The GOOSE subscriber component improperly validates the UTC timestamp field in unauthenticated IEC 61850 GOOSE (EtherType 0x88B8) Layer-2 multicast messages. A specially crafted GOOSE frame containing an undersized timestamp field can trigger a heap out-of-bounds read during message processing, causing the process to crash and resulting in a denial-of-service condition.
OpenClaw Dashboard contains a stored cross-site scripting vulnerability that allows unauthenticated remote attackers to execute arbitrary JavaScript in the administrator's browser session by injecting HTML markup into agent transcript messages processed through the sessions API. Attackers can craft a message containing inline event handler payloads such as an img tag with an onerror attribute within the 60-character rendering budget, which is stored in the session transcript and interpolated unsanitized into innerHTML on the default landing page, allowing theft of session tokens and unauthorized calls to authenticated administrative endpoints including agent instruction file modification.
MeshCentral 1.1.21 contains a cross-site WebSocket hijacking protection bypass vulnerability that allows unauthenticated remote attackers to hijack authenticated administrator sessions by exploiting an unconditional early return in the CheckWebServerOriginName() function within webserver.js when self-signed certificates are in use. Attackers can open cross-origin WebSocket connections to any of the twelve WebSocket endpoints, send crafted action commands to exfiltrate the server sessionKey used to sign session cookies, forge session tokens as arbitrary users, and gain full remote control of all managed devices governed by the MeshCentral instance.
The GOOSE parser contains an off-by-one boundary-handling flaw that can be triggered by a single unauthenticated Layer-2 multicast frame on the process bus. When specific GOOSE message fields are processed, the parser advances its internal buffer position incorrectly, resulting in a heap out-of-bounds read. On affected platforms, this condition reliably terminates the subscriber process and causes a denial-of-service.
The GOOSE payload parser contains a boundary handling flaw that can be triggered by a single unauthenticated Layer 2 multicast frame on the process bus. When processing specific payload fields, an attacker controlled inner element length may exceed its enclosing length, causing the parser to over read by one byte. This out-of-bounds read reliably terminates the subscriber process, resulting in a denial-of-service condition.