Advisory

PYSEC-2026-4012

Also known as: BIT-virtualenv-2026-102938, CVE-2026-102938, GHSA-9h9j-4vrj-gf7g

Summary

virtualenv writes prompt values into pyvenv.cfg without sanitizing line boundaries, allowing configuration injection

Details

pyvenv.cfg is a line-based format with no escape syntax. PyEnvCfg.write()
wrote values verbatim, while PyEnvCfg._read_values() parses the file with
str.splitlines(). A value containing a line boundary therefore became
additional configuration lines, and because reading is last-wins, the injected
keys replaced any key written earlier in the file.

The prompt value is the reachable input: it is set by --prompt, by the
VIRTUALENV_PROMPT environment variable, or from the config file, and
write() emits prompt before home. A crafted prompt can therefore set
home in the generated pyvenv.cfg. home is what tooling reads to locate
the base interpreter, so a consumer that trusts it can be pointed elsewhere.
implementation, version_info, version, executable, command and
virtualenv are also written before prompt and can be replaced the same
way.

This requires the prompt to come from somewhere other than the person running
the command, for example a CI job templating a branch name into it, tooling
deriving an environment name from user-supplied data, or an inherited
VIRTUALENV_PROMPT.

The boundary set is the one str.splitlines() recognizes, which is wider than
\n: \r, \v, \f, the file, group and record separators, U+0085,
U+2028 and U+2029 were all written through unchanged and all split the
line when read back.

Fixed in 21.7.11: PyEnvCfg.write() now collapses those boundaries to spaces
as it serializes each line, so it cannot emit a structurally invalid file
regardless of what a caller places in content.

Severity

Not rated by the source.

Dates

Published
2026-09-17 16:42 UTC
Modified
2026-10-06 15:25 UTC

Affected packages and fixes

virtualenv

PyPI · All systems

Affected

  • introduced 0, fixed 21.7.11 (ecosystem)

Fixed versions

21.7.11

Fix

  • Fixed version 21.7.11
    pip install --upgrade virtualenv==21.7.11

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: PyPA Advisory Database · CC BY 4.0

Sources & licences