Skip to content

AAK-MCP-PENPOT-CVE-2026-100868-001: Penpot MCP plugin WebSocket bridge listens on every interface (below 2.18.0)

Severity
MEDIUM
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
PenpotMcpPluginBridgeAllInterfaces

What it detects

@penpot/mcp, Penpot's MCP server on npm, opens a WebSocket bridge (port 4402 by default) for the Penpot browser plugin. Before Penpot 2.18.0 that bridge is created as new WebSocketServer({ port }) with no host, so it listens on every interface whatever PENPOT_MCP_SERVER_HOST says, and in single-user mode it accepts the connection without authentication. Anyone on an adjacent network can connect as the plugin, receive the agent's task payloads and return forged results (CVE-2026-100868, CVSS 3.1 6.3, GHSA-ch2q-6x56-qg5r). The fix, commit b5274a44 (2026-09-22), is in Penpot's 2.18.0 tag and every 2.18.x tag after it, but their mcp/package.json still reads 2.17.0 (penpot/penpot#12007), so npm never got a 2.18.x build. The first @penpot/mcp on npm with the fix is 2.19.1 (2026-11-10), which binds the bridge to PENPOT_MCP_SERVER_HOST, localhost by default. It is published under the next dist-tag, and latest is still 2.15.4, which binds every interface, as npm's 2.17.0 (2026-07-08) does. The older @penpot/mcp pin, for the REPL RCE fixed in 2.15.0, stays a separate rule because that one is critical and this one is not.

How to fix

Upgrade @penpot/mcp to 2.19.1 or later and pin that version: it is published under the next dist-tag, so npx @penpot/mcp with no version still installs the affected 2.15.4. Leave PENPOT_MCP_SERVER_HOST at localhost unless the bridge must be reached from another host. Until you can upgrade, block the plugin WebSocket port (PENPOT_MCP_WEBSOCKET_PORT, 4402 by default) from every other host, or run the server only on a machine that is not reachable from a shared network.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-PENPOT-CVE-2026-100868-001

Limitations

Reports a reference that names @penpot/mcp: a package.json or lockfile entry, or npx @penpot/mcp in an MCP config, where an unpinned reference is reported because what npm installs by default is affected (re-checked 2026-11-14: latest is 2.15.4, without the fix, and the fixed 2.19.1 is under next). A launch that names a dist-tag, such as npx @penpot/mcp@next, states no version the rule reads and is reported, though next is fixed today. The floor is 2.18.0, Penpot's fixed version; npm has no release between 2.17.0 and 2.19.1, and a build from a Penpot 2.18.x tag calls itself 2.17.0 and would be reported. It reads the npm version, not Penpot's: a self-hosted Penpot 2.18.0 server does not clear an older @penpot/mcp, since the bridge runs in the MCP server. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

References

  • CVE: CVE-2026-100868
  • OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering), MCP07:2025 (Insufficient Authentication & Authorization)
  • OWASP Agentic Top 10: ASI04 (Agentic Supply Chain Vulnerabilities), ASI07 (Insecure Inter-Agent Communication)
  • Adversa AI MCP Top 25 (AAK-defined ids): ADV-AUTH-01 (Missing Authentication)
  • CSA AI Controls Matrix (AICM): IAM-01, IVS-04, STA-08

All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-PENPOT-CVE-2026-100868-001.md: the page then shows that text, with the registry reference appended under it.