CVE-2026-23968: Copier safe template has arbitrary filesystem read access via symlinks when _preserve_symlinks: false
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 include arbitrary files/directories outside the local template clone location by using symlinks along with preservesymlinks: false (which is Copier's default…
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 include arbitrary files/directories outside the local template clone location by using symlinks along with `_preserve_symlinks: false` (which is Copier's default setting).
Imagine, e.g., a malicious template author who creates a template that reads SSH keys or other secrets from well-known locations and hopes for a user to push the generated project to a public location like github.com where the template author can extract the secrets.
Reproducible example:
- Illegally include a file in the generated project via symlink resolution:
echo "s3cr3t" > secret.txt
mkdir src/
pushd src/
ln -s ../secret.txt stolen-secret.txt
popd
uvx copier copy src/ dst/
cat dst/stolen-secret.txt
#s3cr3t- Illegally include a directory in the generated project via symlink resolution:
mkdir secrets/
pushd secrets/
echo "s3cr3t" > secret.txt
popd
mkdir src/
pushd src/
ln -s ../secrets stolen-secrets
popd
uvx copier copy src/ dst/
tree dst/
# dst/
# └── stolen-secrets
# └── secret.txt
#
# 1 directory, 1 file
cat dst/stolen-secrets/secret.txt
# s3cr3tPatches
n/a
Workarounds
n/a
References
n/a
Credited to sisp, cbrown1234.
References
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-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
