Is CVE-2026-113713 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-113713 being exploited in the wild.

How severe is CVE-2026-113713?

Medium severity, with a CVSS score of 4, published 20 October 2026.

Which products and versions are affected?

Pypa Virtualenv 21.14.8 to 21.14.9; virtualenv (PyPI) >= 21.14.8, < 21.14.10, ECOSYSTEM:introduced=21.14.8,fixed=21.14.10.

How is CVE-2026-113713 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-113713?

Check whether you run Pypa Virtualenv or virtualenv (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-113713: virtualenv symlink app-data dangling reference

Q: Is there a fix for CVE-2026-113713?

Yes. virtualenv (PyPI): upgrade to 21.14.10 or later. Until then: Do not use the environment variable VIRTUALENV_SYMLINK_APP_DATA or configure symlink_app_data in virtualenv.ini on shared systems with temporary storage. Recreate any environments that were created with versions 21.14.8 through 21.14.9 if symlink_app_data was enabled. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-113713 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-113713?

Check whether you run Pypa Virtualenv or virtualenv (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-113713 · Severity: medium · CVSS 4 · Published 2026-10-20

virtualenv is a tool that creates isolated Python development environments. A flaw in versions 21.14.8 through 21.14.10 could leave an environment with broken links to package files that are deleted after setup. On shared systems, another user could exploit this by claiming the orphaned cache path, potentially gaining access to or modifying the affected environment.

Technologies: Pypa Virtualenv, virtualenv (PyPI). Vendors: Pypa, PyPI.

Quick answers

Is CVE-2026-113713 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-113713 being exploited in the wild.
How severe is CVE-2026-113713?: Medium severity, with a CVSS score of 4, published 20 October 2026.
Which products and versions are affected?: Pypa Virtualenv 21.14.8 to 21.14.9; virtualenv (PyPI) >= 21.14.8, < 21.14.10, ECOSYSTEM:introduced=21.14.8,fixed=21.14.10.
Is there a fix for CVE-2026-113713?: Yes. virtualenv (PyPI): upgrade to 21.14.10 or later. Until then: Do not use the environment variable VIRTUALENV_SYMLINK_APP_DATA or configure symlink_app_data in virtualenv.ini on shared systems with temporary storage. Recreate any environments that were created with versions 21.14.8 through 21.14.9 if symlink_app_data was enabled. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-113713 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-113713?: Check whether you run Pypa Virtualenv or virtualenv (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

virtualenv (PyPI): upgrade to 21.14.10 or later
```
pip install "virtualenv>=21.14.10"
```

Do not use the environment variable VIRTUALENV_SYMLINK_APP_DATA or configure symlink_app_data in virtualenv.ini on shared systems with temporary storage. Recreate any environments that were created with versions 21.14.8 through 21.14.9 if symlink_app_data was enabled.

Technical details

The app-data seeder in virtualenv can create symlinks to temporary package cache files when symlink_app_data is enabled via environment variable or configuration file, even though the command-line flag guards against this for temporary storage. When virtualenv deletes the temporary cache after environment creation, the symlinks dangle. On shared temporary directories, a different account can occupy that cache pathname before the environment owner uses the environment again, leading to a privilege or isolation boundary violation.

Affected products

pypa virtualenv 21.14.8 to 21.14.9

Identifiers

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

Timeline

2026-10-20: disclosed
2026-10-17: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.