Advisory

RUSTSEC-2026-0394

Also known as: None

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.

Severity

Not rated by the source.

Dates

Published
2026-09-23 12:00 UTC
Modified
2026-10-26 14:00 UTC

Affected packages and fixes

rustpython-vm

crates.io · All systems

Affected

  • introduced 0.3.0, fixed 0.6.0 (semver)

Fixed versions

0.6.0

Fix

  • Fixed version 0.6.0
    cargo update -p rustpython-vm --precise 0.6.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: RustSec Advisory Database · CC0-1.0

Sources & licences