<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T09:26:36.152363+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-53951</id>
    <title>CVE-2026-53951 — Copier: trust-prefix bypass via path traversal runs tasks unprompted</title>
    <updated>2026-09-28T09:26:36.190244+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> copier-org copier</p>
<p>Copier is a library and CLI app for rendering project templates. In versions 9.5.0 through 9.15.1, the `trust` setting's prefix match
(`copier/_settings.py`) compares the template URL against a trusted prefix with a raw `str.startswith` and no path normalization, while the URL is normalized when the template is actually fetched (`Path.resolve()` for local paths; libcurl dot-segment removal for `https`). A template reference that textually starts with a trusted prefix but contains `..` is therefore granted trust yet resolves to a different, attacker-controlled template, whose `tasks` / `migrations` / `jinja_extensions` then run without the `--trust` prompt — arbitrary command execution. Version 9.15.2 patches the issue.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-53951"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-9gmc-jqmh-3rvm</id>
    <title>GHSA-9gmc-jqmh-3rvm — Copier has a trust-prefix bypass via path traversal that runs tasks unprompted</title>
    <updated>2026-09-28T09:26:36.190562+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: copier</p>
<p># Copier: trust-prefix bypass via path traversal runs tasks unprompted</p>
<p>### Summary</p>
<p>In copier `&gt;= 9.5.0, &lt;= 9.15.1`, the `trust` setting's prefix match
(`copier/_settings.py`) compares the template URL against a trusted prefix with
a raw `str.startswith` and **no path normalization**, while the URL *is*
normalized when the template is actually fetched (`Path.resolve()` for local
paths; libcurl dot-segment removal for `https`). A template reference that
textually starts with a trusted prefix but contains `..`
(e.g. `https://github.com/trusted-org/../attacker-org/repo.git`) is therefore
granted trust yet resolves to a different, attacker-controlled template, whose
`tasks` / `migrations` / `jinja_extensions` then run **without the `--trust`
prompt** — arbitrary command execution. Likely **CWE-22 (Improper Limitation of
a Pathname)** in the trust check leading to **CWE-94 (code execution)**.</p>
<p>### Details</p>
<p>`trust` lets users mark template locations as trusted so copier skips the
unsafe-feature gate. A trailing `/` makes an entry a **prefix** match
(`docs/settings.md`: *"Locations ending with `/` will be matched as prefixes,
trusting all templates from that location"*).</p>
<p>`copier/_settings.py:141-146` (tag `v9.15.1`):</p>
<p>```python
    return any(
        repository.startswith(_normalize(t))
        if t.endswith("/")
        else repository == _normalize(t)
        for t in trust
    )
```</p>
<p>`_normalize` only expands `~`; it does **not** touch `..` or collapse segments —
`copier/_set…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-9gmc-jqmh-3rvm"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2026-3818</id>
    <title>PYSEC-2026-3818 — Copier has a trust-prefix bypass via path traversal that runs tasks unprompted</title>
    <updated>2026-09-28T09:26:36.190691+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: copier</p>
<p># Copier: trust-prefix bypass via path traversal runs tasks unprompted</p>
<p>### Summary</p>
<p>In copier `&gt;= 9.5.0, &lt;= 9.15.1`, the `trust` setting's prefix match
(`copier/_settings.py`) compares the template URL against a trusted prefix with
a raw `str.startswith` and **no path normalization**, while the URL *is*
normalized when the template is actually fetched (`Path.resolve()` for local
paths; libcurl dot-segment removal for `https`). A template reference that
textually starts with a trusted prefix but contains `..`
(e.g. `https://github.com/trusted-org/../attacker-org/repo.git`) is therefore
granted trust yet resolves to a different, attacker-controlled template, whose
`tasks` / `migrations` / `jinja_extensions` then run **without the `--trust`
prompt** — arbitrary command execution. Likely **CWE-22 (Improper Limitation of
a Pathname)** in the trust check leading to **CWE-94 (code execution)**.</p>
<p>### Details</p>
<p>`trust` lets users mark template locations as trusted so copier skips the
unsafe-feature gate. A trailing `/` makes an entry a **prefix** match
(`docs/settings.md`: *"Locations ending with `/` will be matched as prefixes,
trusting all templates from that location"*).</p>
<p>`copier/_settings.py:141-146` (tag `v9.15.1`):</p>
<p>```python
    return any(
        repository.startswith(_normalize(t))
        if t.endswith("/")
        else repository == _normalize(t)
        for t in trust
    )
```</p>
<p>`_normalize` only expands `~`; it does **not** touch `..` or collapse segments —
`copier/_set…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2026-3818"/>
  </entry>
</feed>
