Comparison Overview
UC Davis CLEAR Center
UC Davis CLEAR Center
1 Shields Avenue, Davis, 95616, US
Last Update: 02/04/2026
Simply put, we must better understand the role of agriculture in nourishing our world. At the same time, we need to know where to focus our attention for a healthy climate and environment. That is where the Clarity and Leadership for Environmental Awareness and 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
UC Davis CLEAR Center
Los Alamos National Laboratory
Benchmark & Cyber Underwriting Signals
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for UC Davis CLEAR Center in 2026.
Incidents vs Research Services Industry Avg (This Year)
No incidents recorded for Los Alamos National Laboratory in 2026.
Incident History - UC Davis CLEAR Center (X = Date, Y = Severity)
UC Davis CLEAR Center 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
UC Davis CLEAR Center
Los Alamos National Laboratory
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.