Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.4amended

virtualenv: Temporary app-data can leave dangling seed package links

CVE-2026-113713GHSA-4f8h-vr72-p32c

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (virtualenv 21.14.10; virtualenv 21.14.10), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI virtualenv

    Affected
    >= 21.14.8, < 21.14.10
    Fixed in
    21.14.10

  • Bitnami virtualenv

    Affected
    >= 21.14.8, < 21.14.10
    Fixed in
    21.14.10

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
4.4 · CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:L/VI:H/VA:L/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-113713: 0.20% estimated exploitation activity in the next 30 days; percentile 10.40 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The app-data seeder can leave an environment linked to temporary package files that virtualenv deletes when creation finishes. The environment-variable and configuration-file forms of `symlink_app_data` can enable this state even though the command-line flag is disabled for temporary app-data. The resulting environment depends on a cache pathname that its owner no longer controls. Anthropic's OSS Scanner reported this as `ANT-2026-ZOE2GEPC` in `virtualenv-20261015-005`, received on 15 October 2026. This draft records source review and functional remediation checks. The reporter's cross-account code-execution claim has not been independently reproduced.

Affected area Integrity of app-data references after temporary cache cleanup.

Attacker-controlled input Symlink seeding must be enabled through `VIRTUALENV_SYMLINK_APP_DATA` or `symlink_app_data` in the configuration file, and app-data setup must fall back to a temporary directory. A missing or unwritable configured…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 7 · amended ·

    Amended from osv record BIT-virtualenv-2026-113713

  2. Revision 6 · amended ·

    Amended from osv record GHSA-4f8h-vr72-p32c

  3. Revision 5 · amended ·

    Amended from ghsa record GHSA-4f8h-vr72-p32c

  4. Revision 4 · amended ·

    Amended from ghsa record GHSA-4f8h-vr72-p32c

  5. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  6. Revision 2 · amended ·

    Amended from osv record GHSA-4f8h-vr72-p32c

  7. Revision 1 · created ·

    Published from ghsa record GHSA-4f8h-vr72-p32c

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-113713

Advisory: virtualenv: Temporary app-data can leave dangling seed package links
IDs: CVE-2026-113713, GHSA-4f8h-vr72-p32c
Record: https://patchnext.com/advisories/cve-2026-113713 (revision 7, source checked 30 Oct 2026, 07:20 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: virtualenv 21.14.10; virtualenv 21.14.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI virtualenv: affected >= 21.14.8, < 21.14.10; fixed in 21.14.10
- Bitnami virtualenv: affected >= 21.14.8, < 21.14.10; fixed in 21.14.10

## Suggested inspection (read-only)
- `python -m pip show virtualenv`: prints the installed version. Run with the environment that serves production active.
- Bitnami virtualenv: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on virtualenv.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4f8h-vr72-p32c (GitHub-reviewed advisory GHSA-4f8h-vr72-p32c lists affected ranges: PyPI virtualenv >=21.14.8 <21.14.10)
- Verified: https://osv.dev/vulnerability/GHSA-4f8h-vr72-p32c (OSV record GHSA-4f8h-vr72-p32c lists affected ranges: PyPI virtualenv >=21.14.8 <21.14.10 (fixed))
- Verified: https://osv.dev/vulnerability/BIT-virtualenv-2026-113713 (OSV record BIT-virtualenv-2026-113713 lists affected ranges: Bitnami virtualenv >=21.14.8 <21.14.10 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…