<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T03:58:44.157436+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/fkie_cve-2026-105863</id>
    <title>fkie_cve-2026-105863</title>
    <updated>2026-10-08T03:58:44.429673+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-105863"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-66wr-7vmr-p5jq</id>
    <title>GHSA-66wr-7vmr-p5jq — Payload authentication token field handling issue</title>
    <updated>2026-10-08T03:58:44.429770+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: payload</p>
<p>### Impact</p>
<p>Under certain field configurations, Payload could include unintended values in the authentication token issued at login.</p>
<p>You are affected if:</p>
<p>- You use an affected Payload version and have configured a custom field option that maps a field to a reserved authentication claim name.</p>
<p>### Patches
Payload now restricts which field configuration options can influence the contents of the authentication token.</p>
<p>Users should upgrade payload packages to `&gt;= 3.90.0` or `&gt;= 4.0.0-canary.34`.</p>
<p>### Workarounds
There is no complete workaround. Users should upgrade payload packages to `&gt;= 3.90.0` or `&gt;= 4.0.0-canary.34`.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-66wr-7vmr-p5jq"/>
  </entry>
</feed>
