Comparison Overview
Naval Surface Warfare Center, Corona Division
Naval Surface Warfare Center, Corona Division
1999 Fourth Street, Norco, CA, 92860, US
Last Update: 21/02/2026
The official account of Naval Surface Warfare Center, Corona Division. NSWC Corona provides transparency to warfighting readiness through data analytics and assessment, engineering the Fleet’s Live-Virtual-Constructive training environment, and assuring the accuracy of...
BAE Systems
BAE Systems, London, SW1Y 5AD, GB
Last Update: 01/04/2026
At BAE Systems, we help our customers to stay a step ahead when protecting people and national security, critical infrastructure and vital information. We provide some of the world’s most advanced, technology-led defence, aerospace and security solutions and employ a sk...
Compliance Ranges Comparison
Naval Surface Warfare Center, Corona Division
BAE Systems
Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for Naval Surface Warfare Center, Corona Division in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for BAE Systems in 2026.
Incident History - Naval Surface Warfare Center, Corona Division (X = Date, Y = Severity)
Naval Surface Warfare Center, Corona Division cyber incidents detection timeline including parent company and subsidiaries.
Incident History - BAE Systems (X = Date, Y = Severity)
BAE Systems cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Naval Surface Warfare Center, Corona Division
BAE Systems
FAQ
Latest Global CVEs
A vulnerability was identified in Databend up to 1.2.881 on HTTP. This affects the function ClientSessionManager::state_key of the file src/query/service/src/servers/http/v1/session/client_session_manager.rs of the component Tenant Handler. The manipulation leads to authorization bypass. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The pull request to fix this issue awaits acceptance.
A vulnerability was determined in VoltAgent up to 2.1.17. Affected by this issue is the function handleGetMemoryConversation of the file packages/server-core/src/handlers/memory.handlers.ts of the component Memory REST API. Executing a manipulation of the argument conversationId can lead to improper authorization. The attack may be performed from remote. This attack is characterized by high complexity. The exploitation is known to be difficult. The exploit has been publicly disclosed and may be utilized. The pull request to fix this issue awaits acceptance.
A vulnerability was found in SimStudioAI sim up to 0.6.92. Affected by this vulnerability is an unknown functionality in the library apps/sim/lib/core/security/deployment.ts of the component Password Protection Handler. Performing a manipulation results in use of weak hash. The attack is possible to be carried out remotely. The attack's complexity is rated as high. The exploitation appears to be difficult. The exploit has been made public and could be used. The pull request to fix this issue awaits acceptance.
A vulnerability has been found in RAGapp up to 0.1.5. Affected is the function FileHandler.upload_file/FileHandler.remove_file of the file src/ragapp/backend/controllers/files.py of the component Knowledge File Handler. Such manipulation leads to path traversal. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.
A flaw has been found in khoj-ai khoj up to 2.0.0-beta.28. This impacts an unknown function of the file src/khoj/routers/api_chat.py of the component Conversation Sharing Handler. This manipulation of the argument conversation.agent causes incorrect authorization. Remote exploitation of the attack is possible. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.