AI Science Tracker
EN

Patool archive extraction can write outside its intended directory on older Python runtimes

patool · AI involvement attributed to CodeAnt AI offensive engine (specific model not disclosed)

Finding and attribution

Patool before 4.0.5 can create files or directories outside the intended extraction directory when using Python's tarfile module on Python before 3.12. The maintainer documented the correction in release 4.0.5. CodeAnt's individual discovery account credits its offensive engine, while the primary CNA names CodeAnt AI Security as finder. Consequences depend on the extraction process's filesystem permissions.

What to update · patool · patool using Python's tarfile module on Python versions before 3.12

Affected versions: Before 4.0.5.

Fixed in: 4.0.5

Action: Update patool to 4.0.5 or later for the documented correction. The advisory range applies to the specified extraction backend and Python runtime; it does not establish that every older release/configuration was independently tested.

The maintainer's release 4.0.5 changelog documents the correction for Python tarfile extraction on Python below 3.12. CodeAnt also identifies 4.0.5 as fixed. This does not establish installed updates or immunity in unreviewed extraction configurations.

Advisory / fix evidence · checked 21 Nov 2026

Product: patool. AI system: CodeAnt AI offensive engine (specific model not disclosed). Team / organization: CodeAnt AI; patool maintainers.

CVE identifiers: CVE-2026-29509.

AI and human contribution (source account): CodeAnt's first-party case account explicitly attributes discovery to its offensive engine. The primary CNA separately credits CodeAnt AI Security as finder. The underlying learned model and detailed human validation allocation are not disclosed.

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 maintainer's dated 4.0.5 release changelog publicly describes the security fix on 18 May; the CNA publication follows inJune and CodeAnt's AI-attribution article is dated 29 June. Unknown zero-day status is not inferred.

Remediation status: fix documented.

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 18 May 2026. AI attribution dated 29 Jun 2026. Sources checked 21 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Not available · no assessment established here. Documented technical effects: Not available.

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.

No source-backed CVSS assessment is established in this catalog.

Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.

Original evidence

Download this source record (JSON)

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