<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 14:01:47 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-47425</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-47425</link>
      <description>&lt;p&gt;Rattler is a library that provides common functionality used within the conda ecosystem. Prior to version 0.43.2, `EntryPoint::FromStr` in `rattler_conda_types` performs only `.trim()` on the `command` field before the linker joins it onto the install prefix and writes an executable Python script. A malicious `noarch:python` package can ship an `info/link.json` with an entry-point name containing `..`, `/`, `\`, or an absolute path; the resulting file is written outside the prefix (or clobbers an existing in-prefix entry-point such as `bin/pip`) with mode `0o775` on Unix and a copied launcher `.exe` on Windows. This affects the default install path of `pixi install`, `mamba install` via py-rattler, `rattler-build`, and any other consumer of the `rattler` install crate; no flag or post-link-script opt-in is involved. Version 0.43.2 contains a fix for the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Rattler is a library that provides common functionality used within the conda ecosystem. Prior to version 0.43.2, `EntryPoint::FromStr` in `rattler_conda_types` performs only `.trim()` on the `command` field before the linker joins it onto the install prefix and writes an executable Python script. A malicious `noarch:python` package can ship an `info/link.json` with an entry-point name containing `..`, `/`, `\`, or an absolute path; the resulting file is written outside the prefix (or clobbers an existing in-prefix entry-point such as `bin/pip`) with mode `0o775` on Unix and a copied launcher `.exe` on Windows. This affects the default install path of `pixi install`, `mamba install` via py-rattler, `rattler-build`, and any other consumer of the `rattler` install crate; no flag or post-link-script opt-in is involved. Version 0.43.2 contains a fix for the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-47425</guid>
    </item>
    <item>
      <title>GHSA-q53q-5r4j-5729 — rattler has an entry-point path traversal in noarch:python install (arbitrary file write)</title>
      <link>https://db.gcve.eu/vuln/ghsa-q53q-5r4j-5729</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: rattler, PyPI: py-rattler&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`EntryPoint::FromStr` in `rattler_conda_types` performs only `.trim()` on the `command` field before the linker joins it onto the install prefix and writes an executable Python script. A malicious `noarch:python` package can ship an `info/link.json` with an entry-point name containing `..`, `/`, `\`, or an absolute path; the resulting file is written outside the prefix (or clobbers an existing in-prefix entry-point such as `bin/pip`) with mode `0o775` on Unix and a copied launcher `.exe` on Windows. This affects the default install path of `pixi install`, `rattler-build`, some methods in `py-rattler`, and any other consumer of the `rattler` install crate; no flag or post-link-script opt-in is involved.&lt;/p&gt;
&lt;p&gt;Resolved in https://github.com/conda/rattler/pull/2445, released in rattler 0.43.2.&lt;/p&gt;
&lt;p&gt;## Affected&lt;/p&gt;
&lt;p&gt;- Repository: https://github.com/conda/rattler
- Commit: `a0e61a33da8b9d6de712fab2a879fa9da977e6e3` (HEAD at audit time, 2026-05-13 release)
- Downstream consumers reached through the same code path: `prefix-dev/pixi` @ `e640477`
- pixi 0.69.0 and rattler-build 0.65.0 fix this issue&lt;/p&gt;
&lt;p&gt;## Researcher&lt;/p&gt;
&lt;p&gt;Berkant Koc &amp;lt;me@berkoc.com&amp;gt;
PGP: 0C588DFD76204987284213EA0AC529C41F8AA5D6&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: rattler, PyPI: py-rattler&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`EntryPoint::FromStr` in `rattler_conda_types` performs only `.trim()` on the `command` field before the linker joins it onto the install prefix and writes an executable Python script. A malicious `noarch:python` package can ship an `info/link.json` with an entry-point name containing `..`, `/`, `\`, or an absolute path; the resulting file is written outside the prefix (or clobbers an existing in-prefix entry-point such as `bin/pip`) with mode `0o775` on Unix and a copied launcher `.exe` on Windows. This affects the default install path of `pixi install`, `rattler-build`, some methods in `py-rattler`, and any other consumer of the `rattler` install crate; no flag or post-link-script opt-in is involved.&lt;/p&gt;
&lt;p&gt;Resolved in https://github.com/conda/rattler/pull/2445, released in rattler 0.43.2.&lt;/p&gt;
&lt;p&gt;## Affected&lt;/p&gt;
&lt;p&gt;- Repository: https://github.com/conda/rattler
- Commit: `a0e61a33da8b9d6de712fab2a879fa9da977e6e3` (HEAD at audit time, 2026-05-13 release)
- Downstream consumers reached through the same code path: `prefix-dev/pixi` @ `e640477`
- pixi 0.69.0 and rattler-build 0.65.0 fix this issue&lt;/p&gt;
&lt;p&gt;## Researcher&lt;/p&gt;
&lt;p&gt;Berkant Koc &amp;lt;me@berkoc.com&amp;gt;
PGP: 0C588DFD76204987284213EA0AC529C41F8AA5D6&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-q53q-5r4j-5729</guid>
    </item>
    <item>
      <title>PYSEC-2026-2971 — rattler has an entry-point path traversal in noarch:python install (arbitrary file write)</title>
      <link>https://db.gcve.eu/vuln/pysec-2026-2971</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: py-rattler&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`EntryPoint::FromStr` in `rattler_conda_types` performs only `.trim()` on the `command` field before the linker joins it onto the install prefix and writes an executable Python script. A malicious `noarch:python` package can ship an `info/link.json` with an entry-point name containing `..`, `/`, `\`, or an absolute path; the resulting file is written outside the prefix (or clobbers an existing in-prefix entry-point such as `bin/pip`) with mode `0o775` on Unix and a copied launcher `.exe` on Windows. This affects the default install path of `pixi install`, `rattler-build`, some methods in `py-rattler`, and any other consumer of the `rattler` install crate; no flag or post-link-script opt-in is involved.&lt;/p&gt;
&lt;p&gt;Resolved in https://github.com/conda/rattler/pull/2445, released in rattler 0.43.2.&lt;/p&gt;
&lt;p&gt;## Affected&lt;/p&gt;
&lt;p&gt;- Repository: https://github.com/conda/rattler
- Commit: `a0e61a33da8b9d6de712fab2a879fa9da977e6e3` (HEAD at audit time, 2026-05-13 release)
- Downstream consumers reached through the same code path: `prefix-dev/pixi` @ `e640477`
- pixi 0.69.0 and rattler-build 0.65.0 fix this issue&lt;/p&gt;
&lt;p&gt;## Researcher&lt;/p&gt;
&lt;p&gt;Berkant Koc &amp;lt;me@berkoc.com&amp;gt;
PGP: 0C588DFD76204987284213EA0AC529C41F8AA5D6&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: py-rattler&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;`EntryPoint::FromStr` in `rattler_conda_types` performs only `.trim()` on the `command` field before the linker joins it onto the install prefix and writes an executable Python script. A malicious `noarch:python` package can ship an `info/link.json` with an entry-point name containing `..`, `/`, `\`, or an absolute path; the resulting file is written outside the prefix (or clobbers an existing in-prefix entry-point such as `bin/pip`) with mode `0o775` on Unix and a copied launcher `.exe` on Windows. This affects the default install path of `pixi install`, `rattler-build`, some methods in `py-rattler`, and any other consumer of the `rattler` install crate; no flag or post-link-script opt-in is involved.&lt;/p&gt;
&lt;p&gt;Resolved in https://github.com/conda/rattler/pull/2445, released in rattler 0.43.2.&lt;/p&gt;
&lt;p&gt;## Affected&lt;/p&gt;
&lt;p&gt;- Repository: https://github.com/conda/rattler
- Commit: `a0e61a33da8b9d6de712fab2a879fa9da977e6e3` (HEAD at audit time, 2026-05-13 release)
- Downstream consumers reached through the same code path: `prefix-dev/pixi` @ `e640477`
- pixi 0.69.0 and rattler-build 0.65.0 fix this issue&lt;/p&gt;
&lt;p&gt;## Researcher&lt;/p&gt;
&lt;p&gt;Berkant Koc &amp;lt;me@berkoc.com&amp;gt;
PGP: 0C588DFD76204987284213EA0AC529C41F8AA5D6&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/pysec-2026-2971</guid>
    </item>
  </channel>
</rss>
