Comparison Overview
Office of Nuclear Energy | U.S. Department of Energy
Office of Nuclear Energy | U.S. Department of Energy
1000 Independence Ave SW, Washington, 20024, US
Last Update: 21/02/2026
The Office of Nuclear Energy (NE) mission is to advance nuclear power to meet the nation's energy, environmental, and national security needs. Under the guidance of three research objectives, NE resolves barriers to technical, cost, safety, security, and proliferation ...
U.S. Census Bureau
4600 Silver Hill Road, Washington, 20233, US
Last Update: 03/04/2026
The Census Bureau serves as the nation’s leading provider of quality data about its people and economy. We have been headquartered in Suitland, Maryland since 1942, and currently employ about 4,285 staff members. We are part of the U.S. Department of Commerce and overse...
Compliance Ranges Comparison
Office of Nuclear Energy | U.S. Department of Energy
U.S. Census Bureau
Benchmark & Cyber Underwriting Signals
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for Office of Nuclear Energy | U.S. Department of Energy in 2026.
Incidents vs Government Administration Industry Avg (This Year)
No incidents recorded for U.S. Census Bureau in 2026.
Incident History - Office of Nuclear Energy | U.S. Department of Energy (X = Date, Y = Severity)
Office of Nuclear Energy | U.S. Department of Energy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - U.S. Census Bureau (X = Date, Y = Severity)
U.S. Census Bureau cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Office of Nuclear Energy | U.S. Department of Energy
U.S. Census Bureau
FAQ
Latest Global CVEs
PraisonAI before 1.5.115 contains a path traversal vulnerability in MultiAgentMonitor that fails to sanitize agent IDs when building file paths. Attackers can include traversal sequences like ../ in agent IDs to read, write, or overwrite arbitrary files, enabling sensitive disclosure, denial of service, or code execution.
PraisonAI before 1.5.115 contains an information disclosure vulnerability in the MultiAgentLedger component that allows attackers to access sensitive data by registering agents with duplicate IDs. Attackers can exploit the lack of agent ID uniqueness enforcement to share ledger instances and expose system prompts and conversation history between agents.
PraisonAI before 1.5.128 contains a cross-origin agent execution vulnerability in the AGUI endpoint that allows remote attackers to trigger arbitrary agent execution. The POST /agui endpoint lacks authentication and hardcodes Access-Control-Allow-Origin: * headers, combined with Starlette's Content-Type-agnostic JSON parsing, enabling attackers to bypass CORS preflight checks via simple requests and exfiltrate sensitive agent responses including tool execution results and environment data.
PraisonAI before 4.5.128 contains an arbitrary shell command execution vulnerability where the UI modules hardcode approval_mode to auto, overriding administrator configuration from PRAISON_APPROVAL_MODE environment variable. Authenticated attackers can instruct the LLM agent to execute arbitrary shell commands via subprocess.run with shell=True, bypassing the manual approval gate and insufficient command sanitization blocklists.
PraisonAI before 1.5.128 caches tool approval decisions by tool name only, not by invocation arguments, allowing subsequent execute_command calls to bypass approval prompts. Attackers can exploit this by obtaining initial approval for a benign command, then silently exfiltrate API keys and credentials via subsequent shell commands without user consent.