RUSTSEC-2026-0394

See a problem?
Please try reporting it to the source first.

Source

https://rustsec.org/advisories/RUSTSEC-2026-0394

Import Source

https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2026-0394.json

JSON Data

https://api.osv.dev/v1/vulns/RUSTSEC-2026-0394

Published

2026-09-23T12:00:00Z

Modified

2026-10-26T14:00:05Z

Summary

Build environment compiled into the library and readable at runtime

Details

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. Bitbison'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.

Database specific

{
    "license":  "CC0-1.0"
}

References

Affected packages

crates.io / rustpython-vm

Package

Name: rustpython-vm; View open source insights on deps.dev
Purl: pkg:cargo/rustpython-vm

Affected ranges

Type: SEMVER
Events: Introduced

0.3.0

Fixed

0.6.0

Ecosystem specific

{
    "affected_functions":  null,
    "affects":  {
        "arch":  [],
        "functions":  [],
        "os":  []
    }
}