Comparison Overview
Norfolk Naval Shipyard
Norfolk Naval Shipyard
None, None, Portsmouth, VA, US, 23709
Last Update: 19/03/2026
"We are America's Shipyard" We are Norfolk Naval Shipyard (NNSY), continuously driving to excellence and delivering service to the fleet safely with the right quality on schedule and within budget. NNSY is recognized as a world class organization in executing our missi...
NAVAL GROUP
40-42 rue du docteur FInlay, Paris cedex 15, 75732, FR
Last Update: 29/03/2026
As an international naval defence player, Naval Group is a partner for countries seeking to maintain control of their maritime sovereignty. Naval Group develops innovative solutions to meet its customers’ requirements. The group is present throughout the entire life cyc...
Compliance Ranges Comparison
Norfolk Naval Shipyard
NAVAL GROUP
Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for Norfolk Naval Shipyard in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
NAVAL GROUP has 8.26% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Norfolk Naval Shipyard (X = Date, Y = Severity)
Norfolk Naval Shipyard cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NAVAL GROUP (X = Date, Y = Severity)
NAVAL GROUP cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Norfolk Naval Shipyard
NAVAL GROUP
FAQ
Latest Global CVEs
clash-verge-service-ipc before 2.3.0 has a world-reachable IPC endpoint, leading to local privilege escalation.
A vulnerability was identified in theonedev onedev up to 15.0.5. This vulnerability affects the function canAccessIssue of the file /issues/ of the component Pull Request Handler. Such manipulation of the argument issue leads to improper authorization. It is possible to launch the attack remotely. Upgrading to version 15.0.6 is able to resolve this issue. It is advisable to upgrade the affected component.
A vulnerability was determined in theonedev onedev up to 15.0.5. This affects an unknown part of the file /repositories/{projectId}/default-branch of the component REST API. This manipulation of the argument project.defaultBranch causes improper authorization. It is possible to initiate the attack remotely. Upgrading to version 15.0.6 is able to mitigate this issue. Upgrading the affected component is advised.
A vulnerability was found in theonedev onedev up to 15.0.5. Affected by this issue is some unknown functionality of the file /projects/ of the component Parent Project Handler. The manipulation of the argument project.parentId results in improper authorization. The attack may be performed from remote. Upgrading to version 15.0.6 can resolve this issue. It is recommended to upgrade the affected component.
A vulnerability has been found in theonedev onedev up to 15.0.5. Affected by this vulnerability is an unknown functionality of the file /projects. The manipulation of the argument project.forkedFromId leads to improper authorization. The attack is possible to be carried out remotely. Upgrading to version 15.0.6 addresses this issue. Upgrading the affected component is recommended.