LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23968: Copier safe template has arbitrary filesystem read access via symlinks when _preserve_symlinks: false

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 include arbitrary files/directories outside the local template clone location by using symlinks along with `_preserve_symlinks: false` (which is Copier's default setting). Version 9.11.2 patches the issue.

MediumCVSS 6.8Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Copier versions before 9.11.2 can treat a supposedly safe project template as safe while allowing it to read files outside the template directory through symlinks. This matters when developers generate projects from templates they do not fully control. The issue is patched in 9.11.2.

Executive priority

Treat as a focused developer-supply-chain issue. Prioritize teams using Copier with external templates or automated project generation. Update is straightforward and should be scheduled promptly, but current public evidence does not support emergency incident response.

Technical view

CVE-2026-23968 affects copier-org Copier before 9.11.2. With the default `_preserve_symlinks: false`, a safe template can use symlinks to include arbitrary files or directories outside the local template clone. The CVE maps to CWE-61 and has CVSS 4.0 score 6.8 with user interaction required.

Likely exposure

Exposure is mainly developer workstations, build environments, or automation that run Copier against third-party or untrusted templates using versions below 9.11.2. Systems only using trusted templates have lower practical risk, but should still update.

Exploitation context

The public sources do not report active exploitation, and the CVE is not marked KEV. Exploitation requires a user or process to generate from a crafted template. The impact described is confidentiality loss through filesystem reads, not code execution.

Researcher notes

The key security boundary failure is that Copier’s safe-template model did not prevent symlink-based reads outside the template clone when symlinks were not preserved. The provided commit and advisory are the primary sources for patch details; no broader exploit telemetry is provided.

Mitigation direction

  • Upgrade Copier to version 9.11.2 or later.
  • Avoid running Copier against untrusted templates until upgraded.
  • Review vendor advisory for any additional operational guidance.
  • Restrict template sources used in developer and CI workflows.

Validation and detection

  • Inventory installed Copier versions in developer and CI environments.
  • Confirm affected installations are below 9.11.2.
  • Identify workflows that consume third-party Copier templates.
  • Check whether `_preserve_symlinks` defaults are relied on in templates.
Prepared
Confidence
high
Sources
4

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-23968 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.8 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/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
3Source 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.8CVSS 4.0MediumCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

6.8Medium
CVSS 4.0 vector shape for CVE-2026-23968Attack 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:H/VI:N/VA:N/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.