<?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>Thu, 08 Oct 2026 09:07:36 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-105863</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-105863</link>
      <description>&lt;p&gt;Payload is a free and open source headless content management system. In versions after 3.0.0 and before 3.90.0, a custom field option that maps a field to a reserved authentication claim name can place unintended values in the authentication token issued at login. This issue is fixed in version 3.90.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Payload is a free and open source headless content management system. In versions after 3.0.0 and before 3.90.0, a custom field option that maps a field to a reserved authentication claim name can place unintended values in the authentication token issued at login. This issue is fixed in version 3.90.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-105863</guid>
    </item>
    <item>
      <title>GHSA-66wr-7vmr-p5jq — Payload authentication token field handling issue</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-66wr-7vmr-p5jq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: payload&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Under certain field configurations, Payload could include unintended values in the authentication token issued at login.&lt;/p&gt;
&lt;p&gt;You are affected if:&lt;/p&gt;
&lt;p&gt;- You use an affected Payload version and have configured a custom field option that maps a field to a reserved authentication claim name.&lt;/p&gt;
&lt;p&gt;### Patches
Payload now restricts which field configuration options can influence the contents of the authentication token.&lt;/p&gt;
&lt;p&gt;Users should upgrade payload packages to `&amp;gt;= 3.90.0` or `&amp;gt;= 4.0.0-canary.34`.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no complete workaround. Users should upgrade payload packages to `&amp;gt;= 3.90.0` or `&amp;gt;= 4.0.0-canary.34`.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: payload&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Under certain field configurations, Payload could include unintended values in the authentication token issued at login.&lt;/p&gt;
&lt;p&gt;You are affected if:&lt;/p&gt;
&lt;p&gt;- You use an affected Payload version and have configured a custom field option that maps a field to a reserved authentication claim name.&lt;/p&gt;
&lt;p&gt;### Patches
Payload now restricts which field configuration options can influence the contents of the authentication token.&lt;/p&gt;
&lt;p&gt;Users should upgrade payload packages to `&amp;gt;= 3.90.0` or `&amp;gt;= 4.0.0-canary.34`.&lt;/p&gt;
&lt;p&gt;### Workarounds
There is no complete workaround. Users should upgrade payload packages to `&amp;gt;= 3.90.0` or `&amp;gt;= 4.0.0-canary.34`.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-66wr-7vmr-p5jq</guid>
    </item>
  </channel>
</rss>
