PenPot MCP REPL server binds to 0.0.0.0 with unauthenticated /execute endpoint — RCE
CVE-2026-45805 · GHSA-22qr-rp27-j9wm · published 2026-05-19
- Severity
- High
- CVSS score
- 8.8
- Chance of exploitation (EPSS)
- 0.38%
- Fixed in
- 2.15.0
- Exploitation Public proof of concept
- Automatable No
- Technical impact Total
- CISA SSVC
Unauthenticated RCE on any machine running the MCP module. Read files, execute commands, dump environment variables (which often contain database credentials, API keys, secrets). The MCP module isn't part of the default Docker deployment, but developers and teams using the MCP integration for AI-assisted design work would run it locally. In shared development environments or CI/CD, the exposed port is reachable from the network.
Upgrade @penpot/mcp to 2.15.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
Two lines: 1. Add a host parameter to the listen call in ReplServer.ts:89: 2. Add authentication to the /execute endpoint. Even a shared secret from an environment variable would be better than nothing.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @penpot/mcp | npm | < 2.15.0 | 2.15.0 |
- CriticalLiteLLM has SQL Injection in Proxy API key verificationlitellmExploited
- Criticaln8n Vulnerable to Remote Code Execution via Expression Injectionn8n, n8nExploited
- HighLiteLLM has a sandbox escape in custom-code guardraillitellmExploited
- HighLangflow affected by Remote Code Execution via validate_code() exec()langflowExploited
- CriticalJupyter MCP Server: Browser DNS rebinding can hijack the Jupyter backend through management routesjupyter-mcp-server
- Criticalmem0ai Databricks vector store vulnerable to SQL injectionmem0ai
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.