GHSA-6fgx-x7m2-74qm
tracexec has `env` command argument injection via environment variables starting with dash in traced exec events
GHSA-6fgx-x7m2-74qm is a low vulnerability (CVSS 1.0) in tracexec, published October 13, 2025. No source lists public exploit code. Fixed in tracexec 0.14.0.
- Severity
- 1.0 LowCVSS 4.0, GitHub Advisories
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
0.14.0tracexec
Description
Impact
For tracexec's command line reconstruction feature, when a traced process executes another process with a environment variable where the key starts with a dash, tracexec incorrectly shows its commandline where such environment variables could cause argument injection for the env command.
Such an injection is completely at the UI level unless the user tries to copy the command line with the injection and paste it into a terminal to execute it.
A minimal POC is executing env -- -a=b bash --norc in tracexec's TUI mode. The resulting command line of env executing bash would be env -a bash -a=b _=/usr/bin/env /usr/bin/bash --norc in tracexec's TUI, which injects -a=b into env's arguments.
This has very limited effect for security. A local adversarial could leverage this to make tracexec show an inaccurate reconstructed commandline for their executed command. If the user of tracexec decides to copy and run the reconstructed commandline,
there could be injection for env's --block-signal, --default-signal, --ignore-signal, --split-string, --unset, --chdir, --argv0 arguments.
Patches
The fix is https://github.com/kxxt/tracexec/pull/118. Users are advised to upgrade to 0.14.0.
Workarounds
Don't blindly paste and execute commands copied from tracexec that contains environment variable where the key starts with a dash.
Attack profile
How easy it is to exploit
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- Active
What an attacker can affect
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
Affected packages
| Package | Affected | Fixed |
|---|---|---|
tracexeccrates.io | before 0.14.0 | 0.14.0 |
What each source reports
GitHub Advisories Score used
tracexec has `env` command argument injection via environment variables starting with dash in traced exec events
Impact
For tracexec's command line reconstruction feature, when a traced process executes another process with a environment variable where the key starts with a dash, tracexec incorrectly shows its commandline where such environment variables could cause argument injection for the env command.
Such an injection is completely at the UI level unless the user tries to copy the command line with the injection and paste it into a terminal to execute it.
A minimal POC is executing env -- -a=b bash --norc in tracexec's TUI mode. The resulting command line of env executing bash would be env -a bash -a=b _=/usr/bin/env /usr/bin/bash --norc in tracexec's TUI, which injects -a=b into env's arguments.
This has very limited effect for security. A local adversarial could leverage this to make tracexec show an inaccurate reconstructed commandline for their executed command. If the user of tracexec decides to copy and run the reconstructed commandline,
there could be injection for env's --block-signal, --default-signal, --ignore-signal, --split-string, --unset, --chdir, --argv0 arguments.
Patches
The fix is https://github.com/kxxt/tracexec/pull/118. Users are advised to upgrade to 0.14.0.
Workarounds
Don't blindly paste and execute commands copied from tracexec that contains environment variable where the key starts with a dash.
- Record
GHSA-6fgx-x7m2-74qm- CVSS 4.0
- 1.0 Low
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L - Weakness
- CWE-77, CWE-88
- Updated
- 2026-11-02
OSV
tracexec has `env` command argument injection via environment variables starting with dash in traced exec events
Impact
For tracexec's command line reconstruction feature, when a traced process executes another process with a environment variable where the key starts with a dash, tracexec incorrectly shows its commandline where such environment variables could cause argument injection for the env command.
Such an injection is completely at the UI level unless the user tries to copy the command line with the injection and paste it into a terminal to execute it.
A minimal POC is executing env -- -a=b bash --norc in tracexec's TUI mode. The resulting command line of env executing bash would be env -a bash -a=b _=/usr/bin/env /usr/bin/bash --norc in tracexec's TUI, which injects -a=b into env's arguments.
This has very limited effect for security. A local adversarial could leverage this to make tracexec show an inaccurate reconstructed commandline for their executed command. If the user of tracexec decides to copy and run the reconstructed commandline,
there could be injection for env's --block-signal, --default-signal, --ignore-signal, --split-string, --unset, --chdir, --argv0 arguments.
Patches
The fix is https://github.com/kxxt/tracexec/pull/118. Users are advised to upgrade to 0.14.0.
Workarounds
Don't blindly paste and execute commands copied from tracexec that contains environment variable where the key starts with a dash.
- Record
GHSA-6fgx-x7m2-74qm- CVSS 4.0
- 1.0 Low
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L - Weakness
- CWE-77, CWE-88
- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.