<?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-07T23:06:16.238118+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-105849</id>
    <title>fkie_cve-2026-105849</title>
    <updated>2026-10-07T23:06:17.515000+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, users with ordinary read access to other authentication documents in a collection with useAPIKey enabled can obtain active API keys and exercise the target accounts' permissions until those keys are rotated or disabled. 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-105849"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-238x-w2j9-gwwr</id>
    <title>GHSA-238x-w2j9-gwwr — Payload vulnerable to API key disclosure through ordinary document reads</title>
    <updated>2026-10-07T23:06:17.515108+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>Users with read access to other user documents could access their active API keys. An exposed key grants the target account’s permissions until rotated or disabled.</p>
<p>You are affected if:</p>
<p>- An authentication collection enables `useAPIKey`.
- Users have read access to other user documents containing active API keys.</p>
<p>### Patches</p>
<p>Users should upgrade payload packages to `&gt;= 3.90.0` or `&gt;= 4.0.0-canary.34`.</p>
<p>### Workarounds</p>
<p>Disable `useAPIKey` or restrict users to reading only their own authentication document. Rotate any API key that may have been exposed.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-238x-w2j9-gwwr"/>
  </entry>
</feed>
