<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T22:39:42.948737+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/cve-2026-40256</id>
    <title>CVE-2026-40256 — Weblate: Prefix-Based Repository Boundary Check Bypass via Symlink/Junction Path Prefix Collision</title>
    <updated>2026-10-04T22:39:42.950387+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> WeblateOrg weblate</p>
<p>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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-40256"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-ffgh-3jrf-8wvh</id>
    <title>GHSA-ffgh-3jrf-8wvh — Weblate: Prefix-Based Repository Boundary Check Bypass via Symlink/Junction Path Prefix Collision</title>
    <updated>2026-10-04T22:39:42.950441+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: weblate</p>
<p>### 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).</p>
<p>### Patches
* https://github.com/WeblateOrg/weblate/pull/18847</p>
<p>### References
Thanks to [m9nx4u](https://hackerone.com/m9nx4u) for reporting this issue via HackerOne.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-ffgh-3jrf-8wvh"/>
  </entry>
</feed>
