<?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>Wed, 07 Oct 2026 01:49:57 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-105806</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-105806</link>
      <description>&lt;p&gt;Payload is a free and open source headless content management system. In @payloadcms/plugin-mcp versions from 3.61.0 until 3.88.0, an authenticated user can manage MCP API keys outside the intended account, enabling privilege escalation through account takeover. This issue is fixed in version 3.88.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Payload is a free and open source headless content management system. In @payloadcms/plugin-mcp versions from 3.61.0 until 3.88.0, an authenticated user can manage MCP API keys outside the intended account, enabling privilege escalation through account takeover. This issue is fixed in version 3.88.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-105806</guid>
    </item>
    <item>
      <title>GHSA-2q76-m6w6-qgc6 — Payload: Improper access control for MCP API keys</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-2q76-m6w6-qgc6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @payloadcms/plugin-mcp&lt;/p&gt;
&lt;p&gt;### Impact
Under certain conditions, an authenticated user could manage MCP API keys outside their intended account allowing an attacker to escalate privileges through account takeover.&lt;/p&gt;
&lt;p&gt;Applications that do not use `@payloadcms/plugin-mcp` are not affected.&lt;/p&gt;
&lt;p&gt;### Patches
Users should upgrade to `@payloadcms/plugin-mcp` version `3.88.0` or later.&lt;/p&gt;
&lt;p&gt;### Workarounds
Upgrading is recommended. Until then, disable the MCP plugin or restrict MCP API-key management to trusted users.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @payloadcms/plugin-mcp&lt;/p&gt;
&lt;p&gt;### Impact
Under certain conditions, an authenticated user could manage MCP API keys outside their intended account allowing an attacker to escalate privileges through account takeover.&lt;/p&gt;
&lt;p&gt;Applications that do not use `@payloadcms/plugin-mcp` are not affected.&lt;/p&gt;
&lt;p&gt;### Patches
Users should upgrade to `@payloadcms/plugin-mcp` version `3.88.0` or later.&lt;/p&gt;
&lt;p&gt;### Workarounds
Upgrading is recommended. Until then, disable the MCP plugin or restrict MCP API-key management to trusted users.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-2q76-m6w6-qgc6</guid>
    </item>
  </channel>
</rss>
