RUSTSEC-2026-0394 json
Build environment compiled into the library and readable at runtime
published last mo. modified 16d ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
The build script of `rustpython-vm` 0.3.0 through 0.5.0 writes every environment variable of the build into `$OUT_DIR/env_vars.rs`. The crate compiles that file into `_sysconfigdata`'s `build_time_vars`. That module is always compiled.
A binary built in CI with secrets in the environment carries those secrets in clear text. Registry tokens, cloud credentials and API keys are the usual ones. Anyone with the binary can read them with `strings` or from Python.
Version 0.6.0 removes the dump and the include. Users of earlier versions should upgrade, rebuild, and ship new binaries. Every secret that was in the environment of a past build whose output left the build machine should be treated as exposed.
Jacob Finkelman first reported the issue in [#8802](https://github.com/RustPython/RustPython/issues/8802). [Bitbison](https://registry.bitbison.io/cargo/rustpython-vm)'s automated supply chain scanning then detected credential data from the build environment flowing into artifacts that third-party software ships in the wild. The leak was confirmed in the published release binaries of at least four dependants but others have been impacted.
Patch / fix
Is RUSTSEC-2026-0394 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | rustpython-vm | >=0.3.0, <0.6.0 |
0.6.0 |
References
-
github.com
/RustPython/RustPython/pull/8813
web
-
crates.io
/crates/rustpython-vm
package
-
rustsec.org
/advisories/RUSTSEC-2026-0394.html
advisory
-
github.com
/RustPython/RustPython/issues/8802
report
-
github.com
/RustPython/RustPython/issues/9236
report
-
crates.io
/crates/rustpython-vm/0.6.0
package
-
registry.bitbison.io
/cargo/rustpython-vm
web
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.