CVE-2026-34726: Copier `_subdirectory` allows template root escape via parent-directory traversal
Summary Copier's subdirectory setting is documented as the subdirectory to use as the template root. However, the current implementation accepts parent-directory traversal such as .. and uses it directly when selecting the template root. As a result, a template can escape its own directory and make Copier render files from the parent directory without --UNSAFE. Details The relevant code path is: 1.
Published Apr 1, 2026 · Updated Apr 6, 2026
Affected packages
copier
- Ecosystem
- PyPI
- Affected
- < 9.14.1
- Fixed in
- 9.14.1
- Check
pip show copier
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Copier's _subdirectory setting is documented as the subdirectory to use as the template root. However, the current implementation accepts parent-directory traversal such as .. and uses it directly when selecting the template root.
As a result, a template can escape its own directory and make Copier render files from the parent directory without --UNSAFE.
Details
The relevant code path is:
- the template defines
_subdirectory - Copier renders that string
template_copy_rootreturnsself.template.local_abspath / subdir- Copier walks that directory as the template root
Relevant code:
The effective sink is:
subdir = self._render_string(self.template.subdirectory) or ""
return self.template.local_abspath / subdirThere is no check that the resulting path stays inside the template directory.
The documentation for _subdirectory describes it as:
Subdirectory to use as the template root when generating a project.
and explains it as a way to separate template metadata from template source code:
That description fits values like template or poetry, but not ...
PoC
PoC 1: _subdirectory: .. escapes to the parent directory
mkdir -p root/template dst
echo 'loot' > root/loot.txt
printf '%s\n' '_subdirectory: ..' > root/template/copier.yml
copier copy --overwrite root/template dst
find dst -maxdepth 3 -type f | sort
cat dst/loot.txtExpected output includes:
dst/loot.txt
dst/template/copier.yml
lootThis shows Copier is rendering from root/ rather than from root/template/.
Impact
If a user runs Copier on an untrusted template, that template can change the effective template root and make Copier render files from outside the intended template directory.
Practical impact:
- template-root escape via
.. - rendering of parent-directory files that were not meant to be part of the template
- possible without
--UNSAFE
Credited to evipepota, sisp.
References
- https://github.com/copier-org/copier/security/advisories/GHSA-85v3-4m8g-hrh6
- https://nvd.nist.gov/vuln/detail/CVE-2026-34726
- https://github.com/copier-org/copier/commit/cb80a3ffc9c3787de3ed837e04ca29a0ff8ca3df
- https://github.com/copier-org/copier/releases/tag/v9.14.1
- https://github.com/advisories/GHSA-85v3-4m8g-hrh6
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-53951
Copier has a trust-prefix bypass via path traversal that runs tasks unprompted
high8.8Aug 19, 2026CVE-2026-34730
Copier `_external_data` allows path traversal and absolute-path local file read without unsafe mode
medium5.5Apr 1, 2026CVE-2026-23968
Copier safe template has arbitrary filesystem read access via symlinks when _preserve_symlinks: false
medium5.5Jan 21, 2026CVE-2026-23986
Copier safe template has arbitrary filesystem write access via directory symlinks when _preserve_symlinks: true
medium7.1Jan 21, 2026CVE-2025-55201
Copier's safe template has arbitrary filesystem read/write access
high8.5Aug 18, 2025CVE-2025-55214
Copier's safe template has filesystem write access outside destination path
medium6.9Aug 18, 2025
