Comparison Overview
Naval Sea Systems Command (NAVSEA)
Naval Sea Systems Command (NAVSEA)
1333 Isaac Hull Ave SE, Washington Navy Yard, 20376, US
Last Update: 23/03/2026
The Naval Sea Systems Command is comprised of command staff, headquarters directorates, affiliated Program Executive Offices (PEOs) and numerous field activities. Together, we engineer, build, buy and maintain ships, submarines and combat systems that meet the Fleet's c...
L3 Technologies
600 Third Ave, New York, 10016, US
Last Update: 30/03/2026
With headquarters in New York City and approximately 31,000 employees worldwide, L3 develops advanced defense technologies and commercial solutions in pilot training, aviation security, night vision and EO/IR, weapons, maritime systems and space. The company reported 20...
Compliance Ranges Comparison
Naval Sea Systems Command (NAVSEA)
L3 Technologies
Benchmark & Cyber Underwriting Signals
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for Naval Sea Systems Command (NAVSEA) in 2026.
Incidents vs Defense and Space Manufacturing Industry Avg (This Year)
No incidents recorded for L3 Technologies in 2026.
Incident History - Naval Sea Systems Command (NAVSEA) (X = Date, Y = Severity)
Naval Sea Systems Command (NAVSEA) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - L3 Technologies (X = Date, Y = Severity)
L3 Technologies cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Naval Sea Systems Command (NAVSEA)
L3 Technologies
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.