<?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>Sat, 03 Oct 2026 01:48:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-41654 — Weblate is Vulnerable to Authenticated SSRF via Project Backup Import bypassing validate_repo_url</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-41654</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; WeblateOrg weblate&lt;/p&gt;
&lt;p&gt;Weblate is a web based localization tool. Prior to version 5.17.1, an authenticated user with project.add permission (default on hosted Weblate SaaS and for any user holding an active billing/trial plan) can import a crafted project backup ZIP whose components/&amp;lt;name&amp;gt;.json contains an attacker-chosen repo URL pointing at a private address (e.g. http://127.0.0.1:9999/) or using a non-allow-listed scheme (e.g. file://, git://). Weblate persists the component via Component.objects.bulk_create([component])[0], which bypasses Django&amp;#39;s full_clean() and therefore never runs the validate_repo_url validator. The URL is subsequently written verbatim into .git/config by configure_repo(pull=False). This issue has been patched in version 5.17.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; WeblateOrg weblate&lt;/p&gt;
&lt;p&gt;Weblate is a web based localization tool. Prior to version 5.17.1, an authenticated user with project.add permission (default on hosted Weblate SaaS and for any user holding an active billing/trial plan) can import a crafted project backup ZIP whose components/&amp;lt;name&amp;gt;.json contains an attacker-chosen repo URL pointing at a private address (e.g. http://127.0.0.1:9999/) or using a non-allow-listed scheme (e.g. file://, git://). Weblate persists the component via Component.objects.bulk_create([component])[0], which bypasses Django&amp;#39;s full_clean() and therefore never runs the validate_repo_url validator. The URL is subsequently written verbatim into .git/config by configure_repo(pull=False). This issue has been patched in version 5.17.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-41654</guid>
    </item>
    <item>
      <title>GHSA-cwcx-382v-8m9g — Weblate Vulnerable to Authenticated SSRF via Project Backup Import bypassing validate_repo_url</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-cwcx-382v-8m9g</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: weblate&lt;/p&gt;
&lt;p&gt;### Impact
An authenticated user with `project.add` permission (default on hosted Weblate SaaS and for any user holding an active billing/trial plan) can import a crafted project backup ZIP whose `components/&amp;lt;name&amp;gt;.json` contains an attacker-chosen `repo` URL pointing at a **private address** (e.g. `http://127.0.0.1:9999/`) or using a **non-allow-listed scheme** (e.g. `file://`, `git://`). Weblate persists the component via `Component.objects.bulk_create([component])[0]`, which bypasses Django&amp;#39;s `full_clean()` and therefore never runs the `validate_repo_url` validator. The URL is subsequently written verbatim into `.git/config` by `configure_repo(pull=False)`.&lt;/p&gt;
&lt;p&gt;### Patches
* https://github.com/WeblateOrg/weblate/pull/19061
* https://github.com/WeblateOrg/weblate/pull/19062&lt;/p&gt;
&lt;p&gt;### Workarounds
Limiting who can create projects limits the scope.&lt;/p&gt;
&lt;p&gt;### Resources
Weblate thanks @fg0x0 for reporting this vulnerability via GitHub.&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
An authenticated user with `project.add` permission (default on hosted Weblate SaaS and for any user holding an active billing/trial plan) can import a crafted project backup ZIP whose `components/&amp;lt;name&amp;gt;.json` contains an attacker-chosen `repo` URL pointing at a **private address** (e.g. `http://127.0.0.1:9999/`) or using a **non-allow-listed scheme** (e.g. `file://`, `git://`). Weblate persists the component via `Component.objects.bulk_create([component])[0]`, which bypasses Django&amp;#39;s `full_clean()` and therefore never runs the `validate_repo_url` validator. The URL is subsequently written verbatim into `.git/config` by `configure_repo(pull=False)`.&lt;/p&gt;
&lt;p&gt;### Patches
* https://github.com/WeblateOrg/weblate/pull/19061
* https://github.com/WeblateOrg/weblate/pull/19062&lt;/p&gt;
&lt;p&gt;### Workarounds
Limiting who can create projects limits the scope.&lt;/p&gt;
&lt;p&gt;### Resources
Weblate thanks @fg0x0 for reporting this vulnerability via GitHub.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-cwcx-382v-8m9g</guid>
    </item>
  </channel>
</rss>
