LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23986: Copier safe template has arbitrary filesystem write access via directory symlinks when _preserve_symlinks: true

Copier is a library and CLI app for rendering project templates. Prior to version 9.11.2, 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. Version 9.11.2 patches the issue.

MediumCVSS 6.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Copier before 9.11.2 can let a supposedly safe project template write files outside the intended destination folder. A malicious template could overwrite files the user has permission to change. This requires a user to run or apply the malicious template, so the main risk is developer workstation or automation misuse rather than remote compromise.

Executive priority

Treat as a near-term developer tooling fix. It is not currently reported as exploited, but malicious templates could damage source trees, configuration, or local files. Prioritize upgrading Copier where external templates or CI automation are used.

Technical view

CVE-2026-23986 affects copier-org Copier versions before 9.11.2. Safe templates using directory symlinks with `_preserve_symlinks: true` can cause generated paths to resolve outside the destination directory, enabling arbitrary filesystem writes within the invoking user’s permissions. The issue is classified as CWE-61 and scored CVSS 4.0 6.9.

Likely exposure

Organizations using Copier to generate projects from third-party, community, or unreviewed templates are most exposed. Risk also exists in CI or developer tooling where Copier runs with broad write permissions. Environments using only trusted templates have lower exposure, but should still update.

Exploitation context

Sources do not report active exploitation, and the CVE is not marked KEV. Exploitation requires user interaction: someone must run Copier against a malicious or compromised template. The practical impact is file overwrite or disruption within the user account’s filesystem permissions.

Researcher notes

The public advisory identifies the vulnerable condition and fixed version but does not include evidence of exploitation in the wild. Analysis should focus on symlink handling, destination path containment, and behavior when `_preserve_symlinks: true` is present. Avoid assuming products beyond copier-org Copier are affected.

Mitigation direction

  • Upgrade Copier to version 9.11.2 or later.
  • Avoid untrusted Copier templates until upgraded.
  • Review templates that use `_preserve_symlinks: true`.
  • Run Copier with least-privilege filesystem permissions.
  • Check vendor advisory and release notes for any updated guidance.

Validation and detection

  • Inventory Copier versions on developer machines and CI runners.
  • Confirm all detected installations are version 9.11.2 or later.
  • Identify pipelines using third-party or externally maintained Copier templates.
  • Review recent Copier runs for unexpected file changes outside destination paths.
  • Verify template trust controls and approval processes.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-61: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-23986 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.9 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.9CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2026-23986Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
copier-orgcopier< 9.11.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-61 · source CWE mapping

UNIX Symbolic Link (Symlink) Following

UNIX Symbolic Link (Symlink) Following represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.