CVE-2026-47731

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 47% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 theait-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, from 2.x before 2.6.1. Users are recommended to upgrade to version 3.1.1 or 2.6.1.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
72(Attend)
EG Risk 72/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
52.9%
KEV
Not listed

Published

June 5, 2026

Last Modified

July 22, 2026

Advisory Details (3)

Auto-updated Jul 22, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
github Patch Available🟡 PoC Available

Path traversal resulting in arbitrary file append (can be triggered over the network by unauthenticated attacker) · Advisory · NASA-AMMOS/AIT-Core · GitHub

https://github.com/NASA-AMMOS/AIT-Core/security/advisories/GHSA-p462-prxw-mjx4
github_release Patch Available

AIT Core v3.1.1

Patch available: NASA-AMMOS/AIT-Core 3.1.1

https://github.com/NASA-AMMOS/AIT-Core/releases/tag/3.1.1
github_release Patch Available

AIT Core v2.6.1

Patch available: NASA-AMMOS/AIT-Core 2.6.1

https://github.com/NASA-AMMOS/AIT-Core/releases/tag/2.6.1

Vendor Advisories for CVE-2026-47731(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
ait-core1.0.0 ... 2.6.0 (21 versions)2.6.1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 2× in last 7d / 2× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 03:17 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-06-14 23:18 UTCEPSS rescore
  4. 2026-06-13 23:00 UTCEPSS rescore
  5. 2026-06-12 23:12 UTCEPSS rescore
  6. 2026-06-05 18:57 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-47731?
CVE-2026-47731 is a critical vulnerability published on June 5, 2026. 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…
When was CVE-2026-47731 disclosed?
CVE-2026-47731 was first published in the National Vulnerability Database on June 5, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47731 actively exploited?
CVE-2026-47731 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 52.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47731?
CVE-2026-47731 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-47731?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47731, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47731

Explore →

Is Your Infrastructure Affected by CVE-2026-47731?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.