Skip to main content
Menu
CVEs

AIT-GUI unauthenticated code execution via web routes

Affects AIT-GUI 1.0.0 through 2.5.0 when the web server is reachable from other hosts, as the tested source binds to 0.0.0.0. Fixed in 2.5.1.

CVE-2026-77309Published , updated

8.8HighCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 2.5.1
Who is exposed
Not reported

Summary

NASA-AMMOS AIT-GUI has a flaw that lets an attacker on an adjacent network, without logging in or any user action, chain two web routes to run arbitrary Python code with the privileges of the AIT-GUI server process. The attacker gets a normal session cookie without credentials and uses it to carry out the code execution.

Written by a model

Original description

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.

Who should check

Teams running AIT-GUI (ait-gui on pip) 1.0.0 through 2.5.0, especially those with the web server reachable from other hosts.

“>= 1.0.0, <= 2.5.0”

github.com

What to do

Upgrade to a fixed version: 2.5.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-77309 (AIT-GUI route chain allows unauthenticated Python execution in server process), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-77309 (entry last updated 2026-11-20):
Affected:
- NASA-AMMOS AIT-GUI: from 1.0.0, fixed in 2.5.1
Fixed versions: 2.5.1.
Conditions (all must be true for the bug to be hit):
- Affects AIT-GUI versions from 1.0.0 through 2.5.0 (source: https://github.com/NASA-AMMOS/AIT-GUI/security/advisories/GHSA-jrjx-9jjw-747m)
- Web server reachable from other hosts (server binds to 0.0.0.0 in the tested source) (source: https://github.com/NASA-AMMOS/AIT-GUI/security/advisories/GHSA-jrjx-9jjw-747m)
- The /tlm/query request uses a dataDir with no .pcap files, so the route errors before cleanup (source: https://github.com/NASA-AMMOS/AIT-GUI/security/advisories/GHSA-jrjx-9jjw-747m)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, no login, no user action.
CISA KEV: CVE-2026-77309 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77309 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/NASA-AMMOS/AIT-GUI/security/advisories/GHSA-jrjx-9jjw-747m
- https://github.com/NASA-AMMOS/AIT-GUI/commit/beb8fc0813eded89f985d3eb9a73535dd327726d
- https://github.com/NASA-AMMOS/AIT-GUI/blob/2.5.1/CHANGELOG.md
- https://github.com/NASA-AMMOS/AIT-GUI/releases/tag/2.5.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-77309
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77309"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure?/25Unknown. Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.8/10CVSS 8.8, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 47 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 6

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · NASA-AMMOS/AIT-GUI · Advisory GHSA-jrjx-9jjw-747m
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-77309
RecordNVD · CVE-2026-77309
Other links 3
RepositoryGitHub · NASA-AMMOS/AIT-GUI · Commit beb8fc08
RepositoryGitHub · NASA-AMMOS/AIT-GUI · CHANGELOG.md
RepositoryGitHub · NASA-AMMOS/AIT-GUI · Release 2.5.1

Questions about CVE-2026-77309

Is CVE-2026-77309 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

The bug lets a remote party with no login run arbitrary Python code on the AIT-GUI server, with the privileges of the server process.

Source: github.com

Which versions are affected by CVE-2026-77309?

AIT-GUI: from 1.0.0 before 2.5.1.

Source: cve.now feed data

Am I affected, and how do I check?

Versions 1.0.0 through 2.5.0 are in the affected range. The tested source binds the web server to 0.0.0.0, so the server is reachable from other hosts, and the flaw is reached through the /tlm/query route when the supplied dataDir has no .pcap files. To check a setup, compare the installed AIT-GUI version with that range and check whether the web server is bound to 0.0.0.0 or otherwise reachable from other hosts.

Source: github.com

How do I fix CVE-2026-77309?

Upgrade AIT-GUI to 2.5.1 or later, which is the listed fixed version.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.