virtualenv: Seeded files retain permissions from an older cache

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-113720: 0.13% estimated exploitation activity in the next 30 days; percentile 2.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The app-data copy seeder uses shutil.copy, which preserves cached file modes independently of the current umask. A cache populated under permissive permissions can therefore produce files with wider access in later environments. Anthropic's OSS Scanner reported this as `ANT-2026-487MH6OW` in `virtualenv-20261015-005`, received on 15 October 2026.

Affected area Permissions of files copied from app-data into a new environment.

Attacker-controlled input The cache must contain files created with broader permissions than the current environment creator intends. Another account must also be able to traverse the new environment and reach those files. A private parent directory prevents that access. No control of a private live cache is assumed.

Affected code The relevant 21.14.8 source is in copy helpers.

Mechanism The default app-data seeder extracts…

Published by the source

23 Oct 2026, 22:23 UTC

Last modified by the source

29 Oct 2026, 10:55 UTC

Source last checked

30 Oct 2026, 07:20 UTC

1. Revision 7 · amended · 30 Oct 2026

   Amended from osv record BIT-virtualenv-2026-113720

2. Revision 6 · amended · 30 Oct 2026

   Amended from osv record GHSA-fc2g-4w5p-6whm

3. Revision 5 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-fc2g-4w5p-6whm

4. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-fc2g-4w5p-6whm

5. Revision 3 · amended · 24 Oct 2026

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

6. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-fc2g-4w5p-6whm

7. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-fc2g-4w5p-6whm

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

# Patch Next advisory brief: CVE-2026-113720

Advisory: virtualenv: Seeded files retain permissions from an older cache
IDs: CVE-2026-113720, GHSA-fc2g-4w5p-6whm
Record: https://patchnext.com/advisories/cve-2026-113720 (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.9; virtualenv 21.14.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI virtualenv: affected < 21.14.9; fixed in 21.14.9
- Bitnami virtualenv: affected < 21.14.9; fixed in 21.14.9

## 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-fc2g-4w5p-6whm (GitHub-reviewed advisory GHSA-fc2g-4w5p-6whm lists affected ranges: PyPI virtualenv >=0 <21.14.9)
- Verified: https://osv.dev/vulnerability/GHSA-fc2g-4w5p-6whm (OSV record GHSA-fc2g-4w5p-6whm lists affected ranges: PyPI virtualenv >=0 <21.14.9 (fixed))
- Verified: https://osv.dev/vulnerability/BIT-virtualenv-2026-113720 (OSV record BIT-virtualenv-2026-113720 lists affected ranges: Bitnami virtualenv >=0 <21.14.9 (fixed))

Commands are suggestions: review each one before running it.