<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-08T16:00:13.605472+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/fkie_cve-2026-105860</id>
    <title>fkie_cve-2026-105860</title>
    <updated>2026-10-08T16:00:13.634272+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 @payloadcms/plugin-multi-tenant versions before 3.90.0 and canary versions before 4.0.0-canary.34, the default tenant array field access allows an authenticated user to assign the user's own account to other tenants. Deployments that replace the default behavior with secured tenants arrayFieldAccess.create and tenants arrayFieldAccess.update functions are not affected by this behavior. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-105860"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-p96c-xwx8-3cqj</id>
    <title>GHSA-p96c-xwx8-3cqj — Payload has a tenant authorization bypass in Multi-Tenant Plugin</title>
    <updated>2026-10-08T16:00:13.634359+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> npm: @payloadcms/plugin-multi-tenant</p>
<p>## Impact</p>
<p>When using the default tenant array field access, an authenticated user could assign themselves to other tenants.</p>
<p>**You are affected if:**</p>
<p>- You are using `@payloadcms/plugin-multi-tenant`</p>
<p>If you configure the tenants arrayFieldAccess.create/update functions, a secured replacement membership field, you are not affected by this specific default behavior.</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>Configure tenants arrayFieldAccess.create and tenants arrayFieldAccess.update so only trusted users authorized for all tenants can modify memberships.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-p96c-xwx8-3cqj"/>
  </entry>
</feed>
