A severe vulnerability has been discovered in AIT-GUI, the browser-based operator console for NASA/JPL’s AMMOS Instrument Toolkit, that could allow unauthenticated attackers to send spacecraft or instrument commands. The flaw, tracked as GHSA-p9r8-2q67-fp86 and rated 9.4 out of 10 on the CVSS v3.1 scale, affects all versions through 2.5.1 and was patched in version 2.5.2.([thehackernews.com](https://thehackernews.com/2026/08/nasa-ait-gui-flaws-could-let.html))
How the Flaw Works
The AMMOS Instrument Toolkit (AIT) serves as NASA’s framework for ground systems that issue commands to spacecraft and process incoming telemetry; its AIT-GUI module is the web interface used by operators. In affected versions, every network-accessible, state-changing route—including endpoints for commands and scripts—is exposed without authentication, authorization, or protection against cross-site request forgery (CSRF). The default configuration binds the server to 0.0.0.0 on port 8080, meaning it listens on all interfaces by default.([thehackernews.com](https://thehackernews.com/2026/08/nasa-ait-gui-flaws-could-let.html))
Specifically, an attacker who can reach the port can issue arbitrary commands via POST /cmd, run server-side scripts via POST /script/run (including files outside the intended directory via path traversal), and execute sequences via POST /seq.([thehackernews.com](https://thehackernews.com/2026/08/nasa-ait-gui-flaws-could-let.html)) They can also exploit the lack of CSRF protection: the web GUI accepts application/x-www-form-urlencoded bodies, which browsers treat as “simple” requests. This means that a cross-origin POST request from a malicious webpage could trigger these routes without any preflight check.([thehackernews.com](https://thehackernews.com/2026/08/nasa-ait-gui-flaws-could-let.html))
The Fix and Deployment Status
The vulnerability is addressed in AIT-GUI version 2.5.2, released on August 12, 2026. The patch changes the default bind address to localhost (or the configured host), adds a “before_request” hook to compare Origin or Referer headers against the server’s own Host header for unsafe methods (POST, PUT, DELETE, PATCH), and confines /script/run and /seq routes to only serve from configured root directories.([thehackernews.com](https://thehackernews.com/2026/08/nasa-ait-gui-flaws-could-let.html))
However, there are concerns about adoption and visibility. The latest publicly published version on PyPI is 2.4.1 (from July 27, 2023), which still contains the critical flaws—including binding to 0.0.0.0 and unrestricted path usage—yet PyPI’s vulnerability listings don’t include these issues.([thehackernews.com](https://thehackernews.com/2026/08/nasa-ait-gui-flaws-could-let.html)) Another related advisory, CVE-2026-60112, describes the missing authentication issue in versions prior to 2.5.1; it also lacks certain vulnerability metadata in the official databases.([thehackernews.com](https://thehackernews.com/2026/08/nasa-ait-gui-flaws-could-let.html))
Other Related Risks
This weakness is just one of several in the broader NASA ground software ecosystem. For example, NASA’s AIT-Core has an unresolved critical remote-code execution bug, CVE-2024-35058, affecting versions up to and including 2.5.2. There are also additional unreviewed advisories for other NASA-AMMOS ground tools, including path traversal and sequencing-server flaws.([thehackernews.com](https://thehackernews.com/2026/08/nasa-ait-gui-flaws-could-let.html))
No evidence has yet emerged that the flaw has been exploited in operational missions. Still, the nature of this vulnerability means the potential blast radius is large: compromised command or scripting endpoints could affect real spacecraft systems if deployed in environments exposed to untrusted networks.([thehackernews.com](https://thehackernews.com/2026/08/nasa-ait-gui-flaws-could-let.html))
That this flaw was identified through AI-assisted code analysis highlights a growing trend in vulnerability discovery.([thehackernews.com](https://thehackernews.com/2026/08/nasa-ait-gui-flaws-could-let.html))
Attention to NASA’s software stack shows that even systems thought internally secure may have exposure due to default configurations or gaps in governance. The lack of CVE assignment for GHSA-p9r8-2q67-fp86 despite its severity raises questions about visibility and responsibility in open source security. The NASA AMMOS team, ground systems engineers, and organizations that build on AIT-GUI will need to prioritize upgrading to version 2.5.2, securely configure host bindings, and ensure all endpoints are properly authenticated and authorized. Monitoring for additional defects in other ground tools remains essential.
