CVE-2026-100868

Penpot MCP plugin bridge could be impersonated over the network

penpot · Penpot · MCP plugin WebSocket bridge

First documented disclosure · Review checkpoint

Summary

A network peer could intercept tool payloads, forge plugin results or prevent dispatch.

Severity and exploitation evidence

Medium · 5.3/10 · CVSS 4.0. Severity source.

Exploitation not established: Reviewed public sources describe the weakness, a correction or a controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The bridge binds all interfaces independently of the configured server host and accepts an unauthenticated single-user connection.

Conditions required

Network reachability to the plugin bridge in single-user mode.

Potential impact

Tool-channel impersonation and denial of service; this is distinct from the older REPL execution flaw.

Affected versions and configurations

Advisory: through 2.17.2. CNA product ranges distinguish Penpot before 2.18.0 and @penpot/mcp before 2.19.1.

Fix and mitigation status

Penpot 2.18.0 per advisory; @penpot/mcp 2.19.1 per CNA. Verify the installed component rather than assuming matching package versions.

Practical next steps

Upgrade the applicable component and verify its actual bind address and plugin authentication.

Operating lesson

Apply network exposure settings to every listener in an MCP integration.

Evidence and limits

Historical backfill. The advisory and CNA use different package version bounds; the difference is retained. Referenced GHSA-22qr describes a separate REPL component and is not merged into this CVE. CNA publication is 2026-09-27; this is distinct from the earliest reviewed public source and correction dates. VulnCheck assessments: CVSS 4.0 5.3; CVSS 3.1 6.3. Independent review correction: CNA datePublic is 2026-09-22; the original advisory was published 2026-09-25. Use the earlier authority-stated public date while retaining the date distinction.

Sources