AI Science Tracker

Seeded files retain permissions from an older cache

virtualenv (Python virtual environment creation and seeding tool) · AI involvement attributed to Anthropic OSS Scanner (specific model/version not identified in the item-level advisory)

Finding and attribution

The app-data copy seeder used shutil.copy, retaining permissive cached file modes independently of the current umask. If another account can traverse the resulting environment, it may modify seeded files (including executable code) that were copied with broader permissions than intended.

Product: virtualenv (Python virtual environment creation and seeding tool). AI system: Anthropic OSS Scanner (specific model/version not identified in the item-level advisory). Team / organization: Anthropic and Python Packaging Authority (virtualenv maintainers).

CVE identifiers: CVE-2026-113720.

AI and human contribution (source account): The pypa item-level advisory explicitly credits ANT-2026-487MH6OW to Anthropic’s OSS Scanner and includes a scanner repro. Anthropic says its scanner scans using strongest models; this report does not specify a model.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The pypa maintainer advisory publicly identifies an Anthropic OSS Scanner report ID for this individual issue. Anthropic says OSS Scanner sends reports directly from its strongest models; this case has no named model/version. No exploitation or zero-day claim is made.

Remediation status: fix documented. The fix creates destination files using mode 0644 or 0755 for executable sources, filtered by current umask, rather than preserving cached source modes. Put environments under owner-only parent directories and recreate environments with inherited permissive cache modes. The fixed mode policy also does not preserve more-restrictive source modes. Fixed in virtualenv 21.14.9. Deployed patch status is not checked.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 17 Oct 2026. AI attribution dated 17 Oct 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Medium · highest recorded score 4.4. Documented technical effects: data modification.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

CVE-2026-113720: data modification.
Prerequisites / affected scope: A later environment copied from a cache populated under permissive umask can contain files writable by another local account; that account can modify package code..
Exploitation evidence: The cited source does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.

Documented fix: The fix creates destination files using mode 0644 or 0755 for executable sources, filtered by current umask, rather than preserving cached source modes. Put environments under owner-only parent directories and recreate environments with inherited permissive cache modes. The fixed mode policy also does not preserve more-restrictive source modes. Fixed in virtualenv 21.14.9. Deployed patch status is not checked.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases