Critical NASA AIT-GUI Flaw Lets Attackers Issue Spacecraft Commands

Key Takeaways

• A critical vulnerability in NASA/JPL’s AIT-GUI could allow unauthenticated attackers to issue commands to spacecraft and scientific instruments.
• The flaw, rated 9.4 CVSS v3.1, stems from a combination of default insecure network binding and a lack of authentication, authorization, and CSRF protection on critical endpoints.
• Even firewalled deployments are at risk if an operator visits a malicious webpage, enabling cross-origin attacks without direct network exposure or credentials.
• The issue has been patched in AIT-GUI version 2.5.2, released on August 12, 2026.

Critical Flaw in NASA’s Spacecraft Command System Exposes Missions to Remote Attack

A severe security vulnerability within the AMMOS Instrument Toolkit GUI (AIT-GUI), an open-source system developed by NASA/JPL, could permit unauthorized individuals to transmit live commands to active spacecraft and scientific instruments. This critical flaw also allows for the execution of arbitrary scripts and command sequences without any prior authentication.

Security researcher Yuval Elbar from Cycode identified and disclosed this significant issue on August 13, 2026. The vulnerability carries a CVSS v3.1 score of 9.4, indicating its high severity. Fortunately, a patch addressing this flaw was released shortly thereafter in AIT-GUI version 2.5.2 on August 12, 2026.

AIT-GUI: The Frontline for Spacecraft Operations

AIT-GUI serves as the web-based operator console for the AMMOS Instrument Toolkit. This toolkit is a widely adopted open-source framework crucial for developing ground data systems that facilitate communication with spacecraft and instruments, both sending commands and processing telemetry data received in return.

In essence, AIT-GUI is the interface where operators initiate actions that translate into real-world commands sent to hardware in space. This direct link to operational hardware elevates what would typically be a routine web application vulnerability into a potentially catastrophic security incident.

Technical Details of the Vulnerability

According to the advisory, the AIT-GUI web server inadvertently exposes itself to a broader network than intended. Despite an operator’s configuration to restrict the console to localhost, the server silently disregards this setting and hardcodes its listener to bind on 0.0.0.0 across all network interfaces, defaulting to port 8080. This misconfiguration effectively exposes the console to the entire reachable network, regardless of intended restrictions.

Compounding this exposure, several critical endpoints within the application lack fundamental security controls. Crucially, state-changing endpoints fail to enforce authentication, authorization, or cross-site request forgery (CSRF) protection. Specifically, the POST /cmd endpoint directly relays any received command string to the spacecraft command bus. Furthermore, the POST /script/run and POST /seq endpoints enable server-side script execution and command-sequence execution, respectively.

The latter two endpoints are also susceptible to path traversal vulnerabilities (CWE-22) because they construct filesystem paths from unvalidated user input. This flaw allows attackers to access and execute files outside their intended script and sequence directories. The broader issues were categorized under CWE-306 (missing authentication) and CWE-352 (CSRF).

A related, separately tracked flaw, CVE-2026-60112, also describes a missing authentication issue. This vulnerability allows an attacker to obtain a valid session by calling Sessions.create() without any credential verification. Once a session is established, the attacker can invoke handle_cmd() to forward arbitrary commands directly to the AIT command bus. This CVE, published on July 28, 2026, carries an even higher CVSS v3.1 base score of 9.8.

Cross-Origin Attack Vector

The vulnerable endpoints accept standard form-encoded POST requests, which qualify as “simple” CORS requests. This means web browsers deliver them cross-origin without requiring a preflight check. Consequently, even AIT-GUI deployments that are firewalled off from the open internet are not entirely safe.

Should an operator with browser access to the console visit a malicious webpage, that page can silently submit a form in the background, firing commands at the console. This attack path requires no credentials, no direct network exposure, and no user interaction beyond opening the malicious page, making it a particularly insidious threat.

What You Should Do

• Upgrade Immediately: All organizations utilizing AIT-GUI are strongly urged to upgrade to version 2.5.2 without delay.
• Verify Network Exposure: After upgrading, meticulously verify that the console port (default 8080) is not reachable from untrusted networks.
• Review History: For any deployment that may have been exposed prior to patching, review command and sequence history for any unauthorized or anomalous activity.
• Implement Durable Fixes: For teams maintaining or hardening deployments, implement robust authentication, authorization, and CSRF protections on all state-changing routes. Ensure the server binds to its configured host rather than the hardcoded 0.0.0.0. Additionally, confine script and sequence paths using canonicalization checks, mirroring existing safeguards elsewhere in the codebase, such as on the /scripts/load endpoint.

This incident serves as a stark reminder that ground systems and operational technology, despite their specialized nature, are susceptible to common web application vulnerabilities. However, the consequences of exploiting these flaws in such critical systems are measured not in data breaches, but in the potential for real-world hardware manipulation and mission disruption.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.