Race condition in tempfile.TemporaryDirectory cleanup allows deleting files outside the temporary directory
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (python-min 3.14.9, 3.13.18, 3.12.16; libpython 3.14.9, 3.13.18, 3.12.16; python 3.14.9, 3.13.18, 3.12.16), 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.
Affected packages
Bitnami python-min
- Affected
- < 3.12.16>= 3.13.0, < 3.13.18>= 3.14.0, < 3.14.9
- Fixed in
- 3.13.18, 3.14.9, 3.12.16
Bitnami libpython
- Affected
- < 3.12.16>= 3.13.0, < 3.13.18>= 3.14.0, < 3.14.9
- Fixed in
- 3.13.18, 3.14.9, 3.12.16
Bitnami python
- Affected
- < 3.12.16>= 3.13.0, < 3.13.18>= 3.14.0, < 3.14.9
- Fixed in
- 3.13.18, 3.14.9, 3.12.16
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record BIT-python-min-2026-12345 lists affected ranges: Bitnami python-min >=0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record BIT-libpython-2026-12345 lists affected ranges: Bitnami libpython >=0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record BIT-python-2026-12345 lists affected ranges: Bitnami python >=0
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record BIT-python-min-2026-12345 lists affected ranges: Bitnami python-min >=0 =3.13.0 =3.14.0 <3.14.9 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record BIT-python-2026-12345 lists affected ranges: Bitnami python >=0 =3.13.0 =3.14.0 <3.14.9 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record BIT-libpython-2026-12345 lists affected ranges: Bitnami libpython >=0 =3.13.0 =3.14.0 <3.14.9 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 5.9 · CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X · score source
- EPSS
- CVE-2026-12345: 0.34% estimated exploitation activity in the next 30 days; percentile 27.98 (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.
The cleanup of tempfile.TemporaryDirectory is vulnerable to a race condition. An attacker who can modify the tree during cleanup can replace a directory with a symbolic link, causing files outside of the temporary directory to be deleted or have their permissions and file flags reset, with the privileges of the process performing the cleanup. Note that platforms where shutil.rmtree.avoids_symlink_attacks is false, remain affected, and file flags may still be reset outside of the tree on all platforms.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 6 · amended ·
Amended from osv record BIT-libpython-2026-12345
- Revision 5 · amended ·
Amended from osv record BIT-python-min-2026-12345
- Revision 4 · amended ·
Amended from osv record BIT-python-2026-12345
- Revision 3 · amended ·
Amended from osv record BIT-python-min-2026-12345
- Revision 2 · amended ·
Amended from osv record BIT-python-2026-12345
- Revision 1 · created ·
Published from osv record BIT-libpython-2026-12345
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-12345 Advisory: Race condition in tempfile.TemporaryDirectory cleanup allows deleting files outside the temporary directory IDs: CVE-2026-12345 Record: https://patchnext.com/advisories/cve-2026-12345 (revision 6, source checked 30 Oct 2026, 07:10 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: python-min 3.14.9, 3.13.18, 3.12.16; libpython 3.14.9, 3.13.18, 3.12.16; python 3.14.9, 3.13.18, 3.12.16. A vendor fix does not mean a deployment is fixed. ## Affected components - Bitnami python-min: affected < 3.12.16; >= 3.13.0, < 3.13.18; >= 3.14.0, < 3.14.9; fixed in 3.13.18, 3.14.9, 3.12.16 - Bitnami libpython: affected < 3.12.16; >= 3.13.0, < 3.13.18; >= 3.14.0, < 3.14.9; fixed in 3.13.18, 3.14.9, 3.12.16 - Bitnami python: affected < 3.12.16; >= 3.13.0, < 3.13.18; >= 3.14.0, < 3.14.9; fixed in 3.13.18, 3.14.9, 3.12.16 ## Suggested inspection (read-only) - Bitnami python-min: check the installed version with your package manager. - Bitnami libpython: check the installed version with your package manager. - Bitnami python: 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 python-min, libpython, python. - 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://osv.dev/vulnerability/BIT-python-min-2026-12345 (OSV record BIT-python-min-2026-12345 lists affected ranges: Bitnami python-min >=0) - Verified: https://osv.dev/vulnerability/BIT-libpython-2026-12345 (OSV record BIT-libpython-2026-12345 lists affected ranges: Bitnami libpython >=0) - Verified: https://osv.dev/vulnerability/BIT-python-2026-12345 (OSV record BIT-python-2026-12345 lists affected ranges: Bitnami python >=0) - Verified: https://osv.dev/vulnerability/BIT-python-min-2026-12345 (OSV record BIT-python-min-2026-12345 lists affected ranges: Bitnami python-min >=0 =3.13.0 =3.14.0 <3.14.9 (fixed)) - Verified: https://osv.dev/vulnerability/BIT-python-2026-12345 (OSV record BIT-python-2026-12345 lists affected ranges: Bitnami python >=0 =3.13.0 =3.14.0 <3.14.9 (fixed)) - Verified: https://osv.dev/vulnerability/BIT-libpython-2026-12345 (OSV record BIT-libpython-2026-12345 lists affected ranges: Bitnami libpython >=0 =3.13.0 =3.14.0 <3.14.9 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…