p PatchFirst

CVE-2025-55214

CVE-2025-55214 · Copier safe template has filesystem write access outside destination path

This page contains facts from public vulnerability sources. Check the original advisory before updating.

Copier library and CLI app for rendering project templates. From 7.1.0 to before 9.9.1, 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. This vulnerability is fixed in 9.9.1.

CVSS 6.9 · Medium · EPSS 0.3% · Fix available

Published
Updated

Stack: python

Affected products and versions

  • copier

    Versions
    • >= 7.1.0, < 9.9.1: Affected

    No fix published

  • copier PyPI

    Versions
    • 7.1.0
    • 7.2.0
    • 8.0.0
    • 8.1.0
    • 8.2.0
    • 8.3.0
    • 9.0.1
    • 9.1.0
    • 9.1.1
    • 9.2.0
    • 9.3.0
    • 9.3.1
    • 9.4.0
    • 9.4.1
    • 9.5.0
    • 9.6.0
    • 9.7.0
    • 9.7.1
    • 9.8.0
    • 9.9.0
    Affected ranges
    • ECOSYSTEM: ≥ 7.1.0, < 9.9.1

    Update to 9.9.1

Original sources

Check your server →