npm package report

Is @payloadcms/plugin-mcp safe?

1 known vulnerability, worst severity HIGH.

// reach

0 direct dependencies

none carry a known advisory

    0 packages depend on it

    an advisory here reaches each of them

      Create a free accountfor every dependency path, dependent and what to upgrade
      // ai model usage

      Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

      cvss
      0.0
      high

      severity out of 10

      epss
      not scored

      chance of exploitation in 30 days

      xyz score
      not scored

      CyberXYZ composite out of 10

      fig. 01 — GHSA-2q76-m6w6-qgc6, the advisory selected below

      // 1 advisories

      GHSA-2q76-m6w6-qgc6

      HIGHCVE-2026-105806
      // 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.

      Applications that do not use @payloadcms/plugin-mcp are not affected.

      // patches

      Users should upgrade to @payloadcms/plugin-mcp version 3.88.0 or later.

      // workarounds

      Upgrading is recommended. Until then, disable the MCP plugin or restrict MCP API-key management to trusted users.

      // cvss v4.0 vector

      CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

      Attack vector
      Network
      Attack complexity
      Low
      Attack requirements
      None
      Privileges required
      Low
      User interaction
      None
      Confidentiality (vulnerable system)
      High
      Integrity (vulnerable system)
      High
      Availability (vulnerable system)
      None
      Confidentiality (subsequent systems)
      None
      Integrity (subsequent systems)
      None
      Availability (subsequent systems)
      None

      Checked 2026-10-07 at 02:39 UTC. The most recent advisory here was published 2026-10-06. Updated continuously from NVD, GHSA, OSV and CNA feeds.

      Think a verdict here is wrong? Tell us — we respond within 2 business days.