{"answers":{"affected":"3 open source packages ship an affected version, including copier.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55214 exists.","fix":"Upgrade copier to 9.9.1 or later.","what":"CVE-2025-55214 is a medium-severity path traversal vulnerability in copier-org copier, published on 18 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-55214 and fix it if it is affected.\n\nWhat it is: CVE-2025-55214 is a medium-severity path traversal vulnerability in copier-org copier, published on 18 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-55214 exists.\n\nAffected packages and fixed versions:\n- copier (PyPI): affected from 7.1.0; fixed in 9.9.1\n- copier (PyPI): affected from 7.1.0; fixed in 9.9.1\n- copier (PyPI): affected from 7.1.0; fixed in 9.9.1\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-2025-55214/ (Markdown: https://insights.sbomify.com/CVE-2025-55214/index.md)","id":"CVE-2025-55214","markdown":"https://insights.sbomify.com/CVE-2025-55214/index.md","name":"CVE-2025-55214","record":{"aliases":["GHSA-p7q8-grrj-3m8w","PYSEC-2026-1273"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Python template library","requires_auth":"none","summary":"A malicious template can write files outside the destination directory, allowing arbitrary file overwrites via path traversal in Copier.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Copier library and CLI app for rendering project templates. From 7.1.0 to before 9.9.1, Copier suggests that it's safe to generate a project from a safe template, i.e. one that doesn't use unsafe features like custom Jinja extensions which would require passing the --UNSAFE,--trust flag. As it turns out, a safe template can currently write files outside the destination path where a project shall be generated or updated. This is possible when rendering a generated directory structure whose rendered path is either a relative parent path or an absolute path. Constructing such paths is possible using Copier's builtin pathjoin Jinja filter and its builtin _copier_conf.sep variable, which is the platform-native path separator. This way, a malicious template author can create a template that overwrites arbitrary files (according to the user's write permissions), e.g., to cause havoc. This vulnerability is fixed in 9.9.1.","ecosystems":["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":"Copier safe template has filesystem write access outside destination path","id":"CVE-2025-55214","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"Denial of service in DIRIS Digiware M-70","id":"CVE-2025-55221"},"packages":[{"ecosystem":"PyPI","fixed":["9.9.1"],"introduced":["7.1.0"],"last_affected":[],"package":"copier","purl":null,"source":"GHSA-p7q8-grrj-3m8w"},{"ecosystem":"PyPI","fixed":["9.9.1"],"introduced":["7.1.0"],"last_affected":[],"package":"copier","purl":"pkg:pypi/copier","source":"GHSA-p7q8-grrj-3m8w"},{"ecosystem":"PyPI","fixed":["9.9.1"],"introduced":["7.1.0"],"last_affected":[],"package":"copier","purl":"pkg:pypi/copier","source":"PYSEC-2026-1273"}],"prev":{"headline":"OpenFGA Authorization Bypass (Check)","id":"CVE-2025-55213"},"products":["copier"],"published":"2025-08-18","related":[],"sources":[{"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"2025-08-18","vendors":["copier-org"]},"summary":"A malicious template can write files outside the destination directory, allowing arbitrary file overwrites via path traversal in Copier.","url":"https://insights.sbomify.com/CVE-2025-55214/"}