Advisory record · RUSTSEC-2026-0394

Build environment compiled into the library and readable at runtime

No CVSS score

Published by OSV at 23 Sept 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
rustpython-vmcrates.io>=0.3.0, <0.6.00.6.0
Identifiers
RUSTSEC-2026-0394
Published
23 Sept 2026
Updated
26 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions 0.3.0 through 0.5.0 of the rustpython-vm crate embed every environment variable from the build into the compiled library, where they can be read from the binary with simple string tools or from Python. An attacker who obtains a binary built with secrets in its environment, such as registry tokens, cloud credentials or API keys, can recover those secrets in clear text. Upgrade to rustpython-vm 0.6.0 or later, rebuild, and ship new binaries; treat any secret that was present during a past build whose output was distributed as exposed.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

No source has published a CVSS score for this record yet.

  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.