<?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-08T15:13:54.008839+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-105853</id>
    <title>fkie_cve-2026-105853</title>
    <updated>2026-10-08T15:13:54.157590+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 from 3.0.0 before 3.90.0 and canary versions before 4.0.0-canary.34, token refresh responses and password reset responses can independently return hidden or read-restricted fields that the requesting user cannot access. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-105853"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-xgv3-crq2-6f69</id>
    <title>GHSA-xgv3-crq2-6f69 — Payload: Token refresh and password reset responses may expose restricted user fields</title>
    <updated>2026-10-08T15:13:54.157770+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>Token refresh and password reset responses could return fields that the requesting user did not have access to.</p>
<p>You are affected if:</p>
<p>- An authentication collection contains hidden or read-restricted fields.</p>
<p>## Patches</p>
<p>Authentication responses now apply field access and hidden-field filtering before returning user documents. Full user documents remain available server-side for access control.</p>
<p>Users should upgrade Payload packages to `&gt;= 3.90.0` or `&gt;= 4.0.0-canary.34`.</p>
<p>Custom authentication strategies remain responsible for filtering user documents returned through custom responses.</p>
<p>## Workarounds</p>
<p>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-xgv3-crq2-6f69"/>
  </entry>
</feed>
