Security researchers just found a vulnerability in software used by NASA's Jet Propulsion Laboratory. The flaw is in AIT-GUI, the browser-based console that operators use to talk to spacecraft and instruments. And here's the kicker: anyone who can reach the port can send commands. No password. No authentication. Nothing.
Cycode discovered the issue. It's tracked as GHSA-p9r8-2q67-fp86 and has a CVSS score of 9.4. That's critical. The flaw affects AIT-GUI versions 2.5.1 and earlier. A fix is out in version 2.5.2.
Let me break down what this means.
What Is AIT-GUI?
AIT-GUI is the operator console for NASA's AMMOS Instrument Toolkit. This toolkit is used to build ground data systems, the software that sends commands to spacecraft and instruments and processes the telemetry coming back down.
Think of it as the mission control dashboard. And right now, that dashboard has a wide-open door.
The Blast Radius:
"The blast radius of an unauthenticated POST is measured in issued instrument commands, not defaced pages," Cycode said.
Translation: this isn't about someone defacing a website. This is about someone potentially commanding a spacecraft.
What Can an Attacker Do?
If an attacker can reach port 8080 on a system running AIT-GUI, they can:
Send Spacecraft Commands
Via POST /cmd, they can issue arbitrary commands to instruments and spacecraft. That's as bad as it sounds.
Run Server Scripts
Via POST /script/run, they can execute scripts on the server. They can even access files outside the intended directory using path traversal.
Execute Command Sequences
Via POST /seq, they can run command sequences. Again, they can access files outside the intended directory.
Perform CSRF Attacks
Because the routes accept simple requests, a cross-origin POST can reach them without a preflight. If an operator visits a malicious page while logged into the console, an attacker could trigger commands.
Why Did This Happen?
The AIT-GUI NASA spacecraft command flaw comes down to a few basic security failures.
No Authentication
The web server binds to 0.0.0.0 on port 8080 by default. Every state-changing route has no authentication, no authorization, and no CSRF protection. It's like leaving your front door wide open.
CORS Simple Requests
The routes accept application/x-www-form-urlencoded bodies. Browsers treat these as CORS "simple" requests. That means cross-origin POST requests don't trigger a preflight. So an attacker can send commands from any website.
Path Traversal
Two routes build filesystem paths from unvalidated input. Attackers can access files outside the intended directory.
The Fix
Release date for AIT-GUI version 2.5.2 is August 12. There are some important updates in this release:
Localhost Binding
The server is now bound to the configured host. By default, it binds to localhost. That means it's not exposed to the network by default.
CSRF Protection
A before_request hook compares a request's Origin or Referer against the server's own Host for POST, PUT, DELETE, and PATCH requests.
Path Confinement
The /script/run and /seq endpoints are now confined to their configured roots.
What's Still Broken?
The patch fixes the most critical issues. But some things remain.
Still No Authentication
The root route still calls Sessions.create() and issues a session cookie to any request without a credential check. The command route accepts any request carrying that cookie.
Missing Updates to PyPI
The last update to PyPI was made for the version 2.4.1 released in July 2023. Versions 2.5.0, 2.5.1, and 2.5.2 aren't available on PyPI. So users installing from PyPI are still vulnerable.
The AI-Assisted Discovery
Here's something interesting: this flaw was found with AI assistance. The commit fixing the issue includes a Co-Authored-By trailer naming Anthropic's Claude Opus 4.8 model. It adds 18 regression tests.
The Researcher's Take:
"This bug was found the way we think most real research will be done from here on: a human researcher working alongside AI-assisted code analysis," Cycode said.
Older NASA Vulnerabilities
This isn't the only flaw in NASA's ground software. The GitHub Advisory Database has several other unreviewed records:
CVE-2026-47731
Path traversal in the AMMOS Instrument Toolkit. Allows arbitrary file append over the network.
CVE-2026-71214
Critical record for the NASA-AMMOS Aerie/PlanDev sequencing server.
CVE-2026-71289
Critical record for the Asynchronous Network Management System reference implementation.
CVE-2024-35058
Critical remote code execution in NASA AIT-Core. Still has no patched version.
What You Should Do
If you're using AIT-GUI, here's what you need to do right now:
1. Update to 2.5.2
This is the only proper solution. Get it from the official repository.
2. Limit Access to the Port 8080
In case there is no update, limit access to the port 8080. Limit access to the trusted networks only.
3. Watch for Malicious Activities
POST activities to the following paths: /cmd, /script/run and /seq must be watched out for. Check your logs.
4. Use AI-Assisted Code Review
Consider using AI-assisted analysis for security reviews. It worked for the researchers.
The Bottom Line
A critical flaw in NASA's AIT-GUI software allows unauthenticated attackers to send commands to spacecraft. The issue affects versions 2.5.1 and earlier. A patch is available in version 2.5.2.
What You Should Know:
- Attackers without authentication can send spacecraft commands
- CVSS Score: 9.4
- Fixed in: Version 2.5.2
- Discovered using: Code analysis with AI
- NASA’s older vulnerabilities have yet to be patched
What You Should Do:
- Update to AIT-GUI 2.5.2
- Restrict network access
- Watch out for suspicious activity
FAQ Section
What is the AIT-GUI NASA spacecraft command flaw?
This is a critical vulnerability in the NASA's AIT-GUI console that allows unauthenticated users to send arbitrary commands to space craft and instruments. The CVSS score for this vulnerability is 9.4.
Which versions are affected?
Versions 2.5.1 and earlier are affected. The fix is in version 2.5.2.
What can an attacker do?
The attacker will be able to do things such as sending commands to the spacecraft, executing server-side scripts, running commands in sequence, and performing CSRF attacks.
How was the vulnerability discovered?
It was discovered with the use of code analysis with the help of artificial intelligence. Human analyzed the code with the help of AI.
What should organizations do?
Update to AIT-GUI version 2.5.2. Restrict network access if you can't update. Monitor for unauthorized activity.
