{"answers":{"affected":"3 open source packages ship an affected version, including virtualenv.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113719 exists.","fix":"Upgrade virtualenv to 21.14.9 or later.","what":"CVE-2026-113719 is a medium-severity vulnerability in pypa virtualenv, published on 20 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-113719 and fix it if it is affected.\n\nWhat it is: CVE-2026-113719 is a medium-severity vulnerability in pypa virtualenv, published on 20 Oct 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113719 exists.\n\nAffected packages and fixed versions:\n- virtualenv (Bitnami): affected all versions; fixed in 21.14.9\n- virtualenv (PyPI): affected all versions; fixed in 21.14.9\n- virtualenv (PyPI): affected all versions; fixed in 21.14.9\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-113719/ (Markdown: https://insights.sbomify.com/CVE-2026-113719/index.md)","id":"CVE-2026-113719","markdown":"https://insights.sbomify.com/CVE-2026-113719/index.md","name":"CVE-2026-113719","record":{"aliases":["AZL-110121","BIT-virtualenv-2026-113719","DEBIAN-CVE-2026-113719","ECHO-b0db-7316-fd96","GHSA-hhxq-47xx-j5xx","MINI-h9fw-3f73-rhrc","UBUNTU-CVE-2026-113719"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":4.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.9, PipInstall._uninstall_previous_version() accepts existing seed-package metadata and _uninstall_dist() joins entries from top_level.txt and RECORD to site-packages without checking containment. When a reused destination contains distribution metadata influenced by another account, relative traversal, absolute entries, or linked parents can cause app-data reseeding to delete files outside the environment or the environment root with the invoking user's permissions, provided that user has deletion rights over the named paths. The deletion occurs during environment creation before any later use of the environment. Fresh environments without existing package metadata and creation with --clear do not enter this cleanup path. This issue is fixed in version 21.14.9.","ecosystems":["Bitnami","PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"virtualenv: Seed replacement does not contain metadata deletion paths","id":"CVE-2026-113719","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":null,"year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"virtualenv: Seeded files retain permissions from an older cache","id":"CVE-2026-113720"},"packages":[{"ecosystem":"Bitnami","fixed":["21.14.9"],"introduced":["0"],"last_affected":[],"package":"virtualenv","purl":"pkg:bitnami/virtualenv","source":"BIT-virtualenv-2026-113719"},{"ecosystem":"PyPI","fixed":["21.14.9"],"introduced":["0"],"last_affected":[],"package":"virtualenv","purl":null,"source":"GHSA-hhxq-47xx-j5xx"},{"ecosystem":"PyPI","fixed":["21.14.9"],"introduced":["0"],"last_affected":[],"package":"virtualenv","purl":"pkg:pypi/virtualenv","source":"GHSA-hhxq-47xx-j5xx"}],"prev":{"headline":"virtualenv: Xonsh activation literals depend on the script decoding codec","id":"CVE-2026-113718"},"products":["virtualenv"],"published":"2026-10-20","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-27","vendors":["pypa"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-113719/"}