{"answers":{"affected":"1 open source package ship an affected version, including rustpython-vm.","exploited":"There is no known exploitation of RUSTSEC-2026-0394 in the wild and no public exploit code.","fix":"Upgrade rustpython-vm to 0.6.0 or later.","what":"RUSTSEC-2026-0394 is a vulnerability in rustpython-vm, published on 23 Sep 2026."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0394 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0394 is a vulnerability in rustpython-vm, published on 23 Sep 2026. \nExploitation: There is no known exploitation of RUSTSEC-2026-0394 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rustpython-vm (crates.io): affected from 0.3.0; fixed in 0.6.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2026-0394/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0394/index.md)","id":"RUSTSEC-2026-0394","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0394/index.md","name":"RUSTSEC-2026-0394","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The build script of `rustpython-vm` 0.3.0 through 0.5.0 writes every\nenvironment variable of the build into `$OUT_DIR/env_vars.rs`. The crate\ncompiles that file into `_sysconfigdata`'s `build_time_vars`. That module is\nalways compiled.\n\nA binary built in CI with secrets in the environment carries those secrets\nin clear text. Registry tokens, cloud credentials and API keys are the usual\nones. Anyone with the binary can read them with `strings` or from Python.\n\nVersion 0.6.0 removes the dump and the include. Users of earlier versions\nshould upgrade, rebuild, and ship new binaries. Every secret that was in the\nenvironment of a past build whose output left the build machine should be\ntreated as exposed.\n\nJacob Finkelman first reported the issue in\n[#8802](https://github.com/RustPython/RustPython/issues/8802).\n[Bitbison](https://registry.bitbison.io/cargo/rustpython-vm)'s automated\nsupply chain scanning then detected credential data from the build\nenvironment flowing into artifacts that third-party software ships in the\nwild. The leak was confirmed in the published release binaries of at least four\ndependants but others have been impacted.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Build environment compiled into the library and readable at runtime","id":"RUSTSEC-2026-0394","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":["0.6.0"],"introduced":["0.3.0"],"last_affected":[],"package":"rustpython-vm","purl":"pkg:cargo/rustpython-vm","source":"RUSTSEC-2026-0394"}],"products":null,"published":"2026-09-23","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":null,"url":"https://insights.sbomify.com/RUSTSEC-2026-0394/"}