NUL character handling in terminal script reads
Cluster 82887 · environments. Data as of
Nothing open on GitHub. Fix merged in #93411 on 24 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #93411. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where null (NUL) characters in script reads—originating in _read_script_in_env—could corrupt paths or allow dot-sourced and NUL-padded scripts to bypass lifecycle guards. The work involves normalizing or stripping NUL bytes during script ingestion.
Open issues0
Open PRs0
Fixes on record
-
#93411 fix: dot-sourced and NUL-padded scripts no longer bypass the gateway lifecycle guard (#77925 #77927, salvage #77926 #77928)
files:
cron/lifecycle_guard.py,tests/hermes_cli/test_gateway_restart_loop.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#83010 fix(terminal): normalize NUL-bearing script reads · done elsewhere →
#82887,#93411,#77927
Closed issues · 1
- Closed#82887terminal tool: embedded null character in path when command references binary executable (root cause in _read_script_in_env)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- environments
- Merged PRs
- #93411
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 24 Aug 2026