Unauthenticated spacecraft commands via credential-free session creation
Published Jul 29, 2026 · Updated Jul 29, 2026
Missing authentication in NASA AMMOS AIT-GUI before 2.5.1 allows remote attackers to issue arbitrary spacecraft commands. Sessions.create() issues a session cookie without checking credentials, and handle_cmd() accepts that session before publishing parsed commands to the AIT command bus. Network reachability to the AIT-GUI service is sufficient; no prior account or user interaction is required.
Summary
What happened
Missing authentication in NASA AMMOS AIT-GUI before 2.5.1 allows remote attackers to issue arbitrary spacecraft commands. Sessions.create() issues a session cookie without checking credentials, and handle_cmd() accepts that session before publishing parsed commands to the AIT command bus. Network reachability to the AIT-GUI service is sufficient; no prior account or user interaction is required.
The record
- CVE
- CVE-2026-60112
- Published
- Jul 29, 2026
- Updated
- Jul 29, 2026
- Vendor
- NASA AMMOS
- Product
- AIT-GUI
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 2026CVE publishedPublication date reported by the CVE source.
- Jul 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.5.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo