<?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 16:01:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-22251 — wlc may leak API keys due to an insecure API key configuration</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-22251</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; WeblateOrg wlc&lt;/p&gt;
&lt;p&gt;wlc is a Weblate command-line client using Weblate&amp;#39;s REST API. Prior to 1.17.0, wlc supported providing unscoped API keys in the setting. This practice was discouraged for years, but the code was never removed. This might cause the API key to be leaked to different servers.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; WeblateOrg wlc&lt;/p&gt;
&lt;p&gt;wlc is a Weblate command-line client using Weblate&amp;#39;s REST API. Prior to 1.17.0, wlc supported providing unscoped API keys in the setting. This practice was discouraged for years, but the code was never removed. This might cause the API key to be leaked to different servers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-22251</guid>
    </item>
    <item>
      <title>GHSA-9rp8-h4g8-8766 — Weblate wlc has insecure API key configuration</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9rp8-h4g8-8766</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wlc&lt;/p&gt;
&lt;p&gt;### Impact
Historically, wlc supported providing unscoped API keys in the setting. This practice was discouraged for years, but the code was never removed. This might cause the API key to be used against different server.&lt;/p&gt;
&lt;p&gt;### Patches
* https://github.com/WeblateOrg/wlc/pull/1098&lt;/p&gt;
&lt;p&gt;### Workarounds
Remove unscoped `key` from wlc configuration. Only use URL-scoped keys in the `[keys]` sections.&lt;/p&gt;
&lt;p&gt;### References
This issue was reported to us by [wh1zee](https://hackerone.com/wh1zee) via HackerOne.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: wlc&lt;/p&gt;
&lt;p&gt;### Impact
Historically, wlc supported providing unscoped API keys in the setting. This practice was discouraged for years, but the code was never removed. This might cause the API key to be used against different server.&lt;/p&gt;
&lt;p&gt;### Patches
* https://github.com/WeblateOrg/wlc/pull/1098&lt;/p&gt;
&lt;p&gt;### Workarounds
Remove unscoped `key` from wlc configuration. Only use URL-scoped keys in the `[keys]` sections.&lt;/p&gt;
&lt;p&gt;### References
This issue was reported to us by [wh1zee](https://hackerone.com/wh1zee) via HackerOne.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9rp8-h4g8-8766</guid>
    </item>
  </channel>
</rss>
