Comparison Overview
DOE Office of Technology Commercialization
DOE Office of Technology Commercialization
1000 Independence Ave. SW, Washington , DC , US, 20585
Last Update: 20/03/2026
The Office of Technology Commercialization (OTC) connects you with U.S. Department of Energy (DOE)-powered innovation to advance discoveries and commercialize transformative, impactful technologies. Learn how we help groundbreaking scientific discoveries achieve their m...
State of Missouri
301 W High Street PO BOX 809, Jefferson City, Missouri, US, 65101
Last Update: 01/04/2026
Build the Missouri of tomorrow. Ensure a strong foundation today. Join a group of innovative team members focused on driving the State of Missouri forward. As public servants, our team members have the opportunity to produce work that is both lasting and important. Thi...
Compliance Ranges Comparison
DOE Office of Technology Commercialization
State of Missouri
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for DOE Office of Technology Commercialization in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for State of Missouri in 2026.
Incident History - DOE Office of Technology Commercialization (X = Date, Y = Severity)
DOE Office of Technology Commercialization cyber incidents detection timeline including parent company and subsidiaries.
Incident History - State of Missouri (X = Date, Y = Severity)
State of Missouri cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
DOE Office of Technology Commercialization
State of Missouri
FAQ
Latest Global CVEs
Use after free in Aura in Google Chrome prior to 150.0.7871.128 allowed a local attacker to potentially exploit heap corruption via a malicious file. (Chromium security severity: High)
Use after free in Ozone in Google Chrome on Linux prior to 150.0.7871.128 allowed a remote attacker who convinced a user to engage in specific UI gestures to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
Out of bounds read and write in V8 in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Use after free in Cast in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Use after free in Network in Google Chrome prior to 150.0.7871.128 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)