How severe is GHSA-6fgx-x7m2-74qm?

No CVSS score has been assigned to GHSA-6fgx-x7m2-74qm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6fgx-x7m2-74qm?

GHSA-6fgx-x7m2-74qm affects the following packages: tracexec (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-6fgx-x7m2-74qm?

Update tracexec to 0.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6fgx-x7m2-74qm is resolved across your whole dependency graph.

How do I detect GHSA-6fgx-x7m2-74qm in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tracexec, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-6fgx-x7m2-74qm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-6fgx-x7m2-74qm actively exploited in the wild?

No public exploit code has been indexed for GHSA-6fgx-x7m2-74qm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-6fgx-x7m2-74qm published, and has it been updated?

GHSA-6fgx-x7m2-74qm was published on October 13, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

tracexec has `env` command argument injection via environment variables starting with dash in traced exec eventsGHSA-6fgx-x7m2-74qm

Fix: kxxt/tracexec#118

GHSA-6fgx-x7m2-74qm is a security vulnerability in tracexec. A fix is available for tracexec — see the affected versions and patch details below.

Published

Oct 13, 2025

Updated

Oct 13, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 13, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀tracexec

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`tracexec`	all versions	0.14.0`cargo update -p tracexec --precise 0.14.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for tracexec, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update tracexec to 0.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6fgx-x7m2-74qm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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 `

O3 Security · Impact-Aware SCA

Is GHSA-6fgx-x7m2-74qm in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works