CVE-2026-113717: virtualenv: Pip seeding with download omits wheel digest verification

Published Oct 20, 2026
·
Updated

virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.9, PipInvoke.getpipinstallcmd() handles --seeder pip --download by calling getwheel(download=False) and then allowing pip to consult the configured index, bypassing virtualenv's downloadwheel() and verifywheeldigest() path. When virtualenv's default-index PyPI digest comparison remains enabled, an index candidate matching the bundled package and version can therefore be selected without comparison to PyPI SHA-256 metadata. Explicit custom-index settings already opt out of that comparison and remain outside this verification-bypass claim; the demonstrated configuration used a non-PyPI index while leaving the index environment variables unset so the comparison policy remained active. This condition does not independently defeat TLS or establish control of the index response. This issue is fixed in version 21.14.9.

Affected Software

1 affected component
pypi/virtualenv<21.14.9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade virtualenv to a version that resolves this vulnerability.

    Fixed in 21.14.9

Event History

Oct 20, 2026
CVE Published
via MITRE·07:22 PM
Data Sourced
via MITRE·07:22 PM
DescriptionWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected by this verification bypass?

The affected path is virtualenv versions before 21.14.9 when creating an environment with the pip seeder and the --download option. It applies where the default-index PyPI digest-comparison policy remains enabled; explicit custom-index settings already opt out of that comparison and are outside this claim.

2

What does an attacker need to exploit this condition?

An attacker would need an index candidate that matches the bundled package and version so pip can select it. The issue does not by itself defeat TLS or give an attacker control of index responses, and exploitation also requires the --seeder pip --download workflow.

3

How can I determine whether I may have been exposed?

Review environment creation commands and automation for use of --seeder pip --download on virtualenv versions earlier than 21.14.9. Also determine whether index environment variables were unset while the default-index PyPI digest-comparison policy was active.

4

What should be done if affected?

Upgrade virtualenv to version 21.14.9, which fixes the issue. Until then, avoid the affected pip-seeding download workflow where possible.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203