Comparison Overview
NIH Clinical Center (CC)
NIH Clinical Center (CC)
10 Center Dr, Bethesda, 20814, US
Last Update: 05/04/2026
Official account of the NIH Clinical Center Privacy policy: http://go.usa.gov/x9svN Comment policy: https://bit.ly/3G6xq94 Engagement ≠ endorsement Since 1953, the NIH Clinical Center, the world's largest hospital dedicated to clinical research, has pioneered research...
Los Alamos National Laboratory
P.O. Box 1663, Los Alamos, NM, US, 87545
Last Update: 29/03/2026
Los Alamos National Laboratory is one of the world’s most innovative multidisciplinary research institutions. We're engaged in strategic science on behalf of national security to ensure the safety and reliability of the U.S. nuclear stockpile. Our workforce specializes ...
Compliance Ranges Comparison
NIH Clinical Center (CC)
Los Alamos National Laboratory
Benchmark & Cyber Underwriting Signals
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for NIH Clinical Center (CC) in 2026.
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for Los Alamos National Laboratory in 2026.
Incident History - NIH Clinical Center (CC) (X = Date, Y = Severity)
NIH Clinical Center (CC) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Los Alamos National Laboratory (X = Date, Y = Severity)
Los Alamos National Laboratory cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
NIH Clinical Center (CC)
Los Alamos National Laboratory
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.