CVE-2026-77309NASA-AMMOS AIT-GUI path traversal
CVE-2026-77309 is a path traversal in NASA-AMMOS AIT-GUI, rated high (8.8 on CVSS 3.1).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Received
What it is
A file name from the request can climb out of the intended folder with sequences like ../, reaching files the service never meant to expose. Temporary files or resources are left behind where others can find them.
How it is reached
An attacker can exploit it from the same local network segment, without an account, and nobody has to click anything.
What an attacker gains
A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker read or write files outside the folders the service meant to expose.
Is it being exploited?
CISA's SSVC assessment notes a public proof of concept.
What to do
- Upgrade NASA-AMMOS AIT-GUI to 2.5.1 or later.
- Segment the networks that can reach it.
Description from NVD
AIT GUI provides a framework for building custom websites for real-time telemetry monitoring, commanding, and other mission operations. From 1.0.0 until 2.5.1, POST /tlm/query in ait/gui/__init__.py writes attacker-controlled field data to fields_in.txt, and its no-PCAP error path can abort before deleting that file. The unauthenticated POST /script/run route accepts a scriptPath that resolves outside ScriptRoot, reads the selected file, and executes it as Python. A network-reachable attacker can obtain the ordinary session cookie without credentials, combine the two routes, and execute arbitrary Python code with the AIT-GUI server process privileges. This issue is fixed in version 2.5.1.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- File storage the service can read or write. The flaw sits between the application and the file system it can reach.
- Error responses, logs and debug endpoints. The flaw sits between internal data and whoever can read the response or log.
- APIs that over-share. The flaw sits between internal data and whoever can read the response or log.
Trust boundaries in play
- Local network segment. The attacker must share a network segment with the target.
- Between the application and the file system it can reach. An attacker who crosses it can read or write files outside the folders the service meant to expose.
- Between internal data and whoever can read the response or log. An attacker who crosses it can learn data or internals that help a follow-up attack.
Questions to answer about your own systems
- Where does NASA-AMMOS AIT-GUI run in your systems, and at which version?
- Which network segments can reach them?
- What can it reach once compromised: which data stores, secrets and services?
14-day free trial
Understand how your systems connect.
See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.
Read more
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.