<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 16:45:28 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68581 — Vikunja 0.22.0 through 2.3.0 Authentication Bypass via Principal ID Collision</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68581</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; go-vikunja vikunja&lt;/p&gt;
&lt;p&gt;Vikunja versions 0.22.0 through 2.3.0 fail to validate the principal type in API token management. Because user IDs and link-share IDs are independent numeric sequences and both resolve through a generic web.Auth.GetID() interface, a link-share JWT whose numeric ID equals a target user&amp;#39;s ID is treated as that user by the /api/v1/tokens endpoints. An authenticated attacker can obtain a target&amp;#39;s numeric user ID via authenticated user search, then create link shares on an attacker-writable project until the link-share sequence reaches that value, and use the resulting link-share JWT to list, create, and delete the target user&amp;#39;s API tokens (including issuing a new token with attacker-chosen scopes under the target&amp;#39;s permissions). Fixed in version 2.4.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; go-vikunja vikunja&lt;/p&gt;
&lt;p&gt;Vikunja versions 0.22.0 through 2.3.0 fail to validate the principal type in API token management. Because user IDs and link-share IDs are independent numeric sequences and both resolve through a generic web.Auth.GetID() interface, a link-share JWT whose numeric ID equals a target user&amp;#39;s ID is treated as that user by the /api/v1/tokens endpoints. An authenticated attacker can obtain a target&amp;#39;s numeric user ID via authenticated user search, then create link shares on an attacker-writable project until the link-share sequence reaches that value, and use the resulting link-share JWT to list, create, and delete the target user&amp;#39;s API tokens (including issuing a new token with attacker-chosen scopes under the target&amp;#39;s permissions). Fixed in version 2.4.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68581</guid>
    </item>
  </channel>
</rss>
