CVE-2026-47731

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-05. A secondary CVSS source baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-47011 (ENISA EUVD) · GHSA-p462-prxw-mjx4 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
59th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 5, 2026

Last Modified

October 24, 2026

Advisory Details (3)

Auto-updated Sep 16, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

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.

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipait-core @ 3.1.1 (fixes = 3.1.0)—ghsa
pipait-core @ 2.6.1 (fixes < 2.6.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
ait-core1.0.0 ... 3.1.0 (22 versions)
  • 3.1.0 up to 3.1.1: fixed in 3.1.1
  • every version up to 2.6.1: fixed in 2.6.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 59× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 149 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 49 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  2. 2026-11-02 04:04 UTCEG score recompute
  3. 2026-11-02 04:04 UTCGHSA enrichmentGHSA-p462-prxw-mjx4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  5. 2026-11-01 07:47 UTCGHSA enrichmentGHSA-p462-prxw-mjx4 · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-11-01 07:47 UTCEG score recompute
  7. 2026-11-01 03:25 UTCEG score recompute
  8. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  9. 2026-10-31 02:47 UTCEG score recompute
  10. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  11. 2026-10-30 02:10 UTCEG score recompute
  12. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  13. 2026-10-29 01:33 UTCEG score recompute
  14. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  15. 2026-10-28 00:56 UTCEG score recompute
  16. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  17. 2026-10-27 00:16 UTCEG score recompute
  18. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  19. 2026-10-25 20:04 UTCEG score recompute
  20. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  21. 2026-10-25 14:24 UTCEG score recompute
  22. 2026-10-24 19:26 UTCEG score recompute
  23. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  24. 2026-10-23 23:39 UTCEG score recompute
  25. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.9% · 58th percentile
Show 75 more
  1. 2026-10-22 23:01 UTCEG score recompute
  2. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  3. 2026-10-21 22:24 UTCEG score recompute
  4. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  5. 2026-10-20 21:45 UTCEG score recompute
  6. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  7. 2026-10-19 21:08 UTCEG score recompute
  8. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  9. 2026-10-18 20:04 UTCEG score recompute
  10. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  11. 2026-10-18 03:35 UTCEG score recompute
  12. 2026-10-17 19:24 UTCEG score recompute
  13. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  14. 2026-10-16 18:46 UTCEG score recompute
  15. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  16. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  17. 2026-10-15 15:49 UTCEG score recompute
  18. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  19. 2026-10-14 10:00 UTCEG score recompute
  20. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  21. 2026-10-13 08:08 UTCEG score recompute
  22. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  23. 2026-10-12 16:01 UTCEG score recompute
  24. 2026-10-11 19:44 UTCEG score recompute
  25. 2026-10-11 16:59 UTCEG score recompute
  26. 2026-10-11 14:23 UTCEG score recompute
  27. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  28. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  29. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  30. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  31. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  32. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  33. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  34. 2026-10-03 19:21 UTCOSV refresh
  35. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  36. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  37. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  38. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  39. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  40. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  41. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  42. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  43. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  44. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  45. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  46. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  47. 2026-09-14 05:00 UTCEG score recompute
  48. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  49. 2026-09-13 04:39 UTCOSV refresh
  50. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  51. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  52. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  53. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  54. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  55. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  56. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  57. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  58. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.9% · 56th percentile
  59. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  60. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  61. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  62. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  63. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.9% · 55th percentile
  64. 2026-08-25 01:49 UTCEG score recompute
  65. 2026-08-23 12:23 UTCEG score recompute
  66. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  67. 2026-08-22 00:26 UTCEG score recompute
  68. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  69. 2026-08-21 02:19 UTCEG score recompute
  70. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  71. 2026-08-20 09:37 UTCEG score recompute
  72. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  73. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.8% · 53rd percentile
  74. 2026-08-17 15:18 UTCEG score recompute
  75. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.8% · 53rd percentile

Frequently asked(5)

What is CVE-2026-47731?
CVE-2026-47731 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-47731 published?
The CVE record for CVE-2026-47731 was published on June 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-47731 actively exploited?
CVE-2026-47731 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47731?
CVE-2026-47731 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47731?
A fix for CVE-2026-47731 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47731 are linked in the Vendor Advisories panel on this page.

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.