<?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://cve.radiocsirt.org</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>Sun, 04 Oct 2026 21:47:06 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-291676</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-291676</link>
      <description>EUVD-2026-291676</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-291676</guid>
    </item>
    <item>
      <title>fkie_cve-2026-40256</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-40256</link>
      <description>&lt;p&gt;Weblate is a web based localization tool. In versions prior to 5.17, repository-boundary validation relies on string prefix checks on resolved absolute paths. In multiple code paths, the check uses startswith against the repository root path. This is not path-segment aware and can be bypassed when the external path shares the same string prefix as the repository path (for example, repo and repo_outside). This issue has been fixed in version 5.17.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Weblate is a web based localization tool. In versions prior to 5.17, repository-boundary validation relies on string prefix checks on resolved absolute paths. In multiple code paths, the check uses startswith against the repository root path. This is not path-segment aware and can be bypassed when the external path shares the same string prefix as the repository path (for example, repo and repo_outside). This issue has been fixed in version 5.17.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-40256</guid>
    </item>
    <item>
      <title>GHSA-ffgh-3jrf-8wvh — Weblate: Prefix-Based Repository Boundary Check Bypass via Symlink/Junction Path Prefix Collision</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ffgh-3jrf-8wvh</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: weblate&lt;/p&gt;
&lt;p&gt;### Impact
Weblate repository-boundary validation relies on string prefix checks on resolved absolute paths. In multiple code paths, the check uses startswith against the repository root path. This is not path-segment aware and can be bypassed when the external path shares the same string prefix as the repository path (for example, repo and repo_outside).&lt;/p&gt;
&lt;p&gt;### Patches
* https://github.com/WeblateOrg/weblate/pull/18847&lt;/p&gt;
&lt;p&gt;### References
Thanks to [m9nx4u](https://hackerone.com/m9nx4u) for reporting this issue via HackerOne.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: weblate&lt;/p&gt;
&lt;p&gt;### Impact
Weblate repository-boundary validation relies on string prefix checks on resolved absolute paths. In multiple code paths, the check uses startswith against the repository root path. This is not path-segment aware and can be bypassed when the external path shares the same string prefix as the repository path (for example, repo and repo_outside).&lt;/p&gt;
&lt;p&gt;### Patches
* https://github.com/WeblateOrg/weblate/pull/18847&lt;/p&gt;
&lt;p&gt;### References
Thanks to [m9nx4u](https://hackerone.com/m9nx4u) for reporting this issue via HackerOne.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ffgh-3jrf-8wvh</guid>
    </item>
    <item>
      <title>PYSEC-2026-2315</title>
      <link>https://cve.radiocsirt.org/vuln/pysec-2026-2315</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: weblate&lt;/p&gt;
&lt;p&gt;Weblate is a web based localization tool. In versions prior to 5.17, repository-boundary validation relies on string prefix checks on resolved absolute paths. In multiple code paths, the check uses startswith against the repository root path. This is not path-segment aware and can be bypassed when the external path shares the same string prefix as the repository path (for example, repo and repo_outside). This issue has been fixed in version 5.17.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: weblate&lt;/p&gt;
&lt;p&gt;Weblate is a web based localization tool. In versions prior to 5.17, repository-boundary validation relies on string prefix checks on resolved absolute paths. In multiple code paths, the check uses startswith against the repository root path. This is not path-segment aware and can be bypassed when the external path shares the same string prefix as the repository path (for example, repo and repo_outside). This issue has been fixed in version 5.17.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/pysec-2026-2315</guid>
    </item>
  </channel>
</rss>
