CVE-2026-47731
published 2026-07-21CVE-2026-47731: The AMMOS Instrument Toolkit (Formerly the Bespoke Links to Instruments for Surface and Space (BLISS)) is a Python-based software suite developed to handle…
PriorityP264critical9.1CVSS 3.1
AVNACLPRNUINSUCNIHAH
EPSS
0.86%
57.0th percentile
The AMMOS Instrument Toolkit (Formerly the Bespoke Links to Instruments for Surface and Space (BLISS)) is a Python-based software suite developed to handle Ground Data System (GDS), Electronic Ground Support Equipment (EGSE), commanding, telemetry uplink/downlink, and sequencing for instrument and CubeSat Missions. In versions prior to 2.6.1 and in version 3.1.0, the Binary Stream Capture (BSC) component exposes an unauthenticated HTTP API for dynamically creating packet capture "handlers." Because the code blindly trusts path‑related form fields, a remote client can bypass the configured log root and direct BSC to log to arbitrary filesystem paths (path traversal / directory escape), and append attacker‑controlled data to those files, using the privileges of the`ait-bsc` process. There are two ways for a remote attacker to trigger this. First, if the attacker has access to the network where `ait-bsc` is deployed (a reason for that could be that the ports are publicly accessible), the payloads can be directly sent to the server to trigger the arbitrary file append. This type of attack is demonstrated in `python_poc.py`. Second, even if the attacker does not have direct access to the network because the software is running in a local network, it is possible to exploit this if a bad actor in that network opens an attacker-controlled website (which might be a website created by an attacker, or a third-party website compromised by the attacker). The browser javascript can automatically send the requests necessary to exploit this into the local network. This is even possible if the server is only accessible on `localhost`. This type of attack is demonstrated by `attacker_tcp.py` and `test1.html` (first launch the attacker TCP server, then start a webserver to host `test1.html`, for example using `python3 -m http.server 7000`, and open `test1.html`).This issue affects BSC (Binary Stream Capture) and usage of the ait-bsc server. This impacts AIT-Core versions before 3.1.1,
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| nasa-ammos | ait-core | < 2.6.1 | 2.6.1 |
| nasa-ammos | ait-core | — | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
NASA-AMMOS AIT-Core up to 2.6.0/3.1.0 Binary Stream Capture path traversal
vuldb·2026-07-22·CVSS 9.1
CVE-2026-47731 [CRITICAL] NASA-AMMOS AIT-Core up to 2.6.0/3.1.0 Binary Stream Capture path traversal
A vulnerability marked as very critical has been reported in NASA-AMMOS AIT-Core up to 2.6.0/3.1.0. This impacts an unknown function of the component Binary Stream Capture. This manipulation causes path traversal.
This vulnerability is handled as CVE-2026-47731. The attack can be initiated remotely. There is not any exploit available.
GHSA
NASA AMMOS Instrument Toolkit: Path traversal resulting in arbitrary file append (can be triggered over the network by unauthenticated attacker)
ghsa·2026-06-05
CVE-2026-47731 [CRITICAL] CWE-22 NASA AMMOS Instrument Toolkit: Path traversal resulting in arbitrary file append (can be triggered over the network by unauthenticated attacker)
NASA AMMOS Instrument Toolkit: Path traversal resulting in arbitrary file append (can be triggered over the network by unauthenticated attacker)
## 1. Summary
The Binary Stream Capture (BSC) component exposes an unauthenticated HTTP API for dynamically creating packet capture “handlers.” Because the code blindly trusts path‑related form fields, a remote client can:
- **Bypass the configured log root** and direct BSC to log to **arbitrary filesystem paths** (path traversal / directory escape), and
- **Append attacker‑controlled data** to those files, using the privileges of the`ait-bsc` process.
There are two ways for a remote attacker to trigger this:
1. If the attacker has access to the network where `ait-bsc` is deployed (a reason for that could be that the ports are publicly accessi
No detection rules found.
No public exploits indexed.
2026-07-21
Published