Apify Model Context Protocol (MCP) server: Domain Allowlist Bypass in fetch-apify-docs via String Prefix Matching
CVE-2026-46341 · GHSA-jwp7-wg77-3w9v · published 2026-05-19
- Severity
- Medium
- CVSS score
- 6.1
- Chance of exploitation (EPSS)
- 0.23%
- Fixed in
- 0.9.21
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
Prompt injection via fetched content: Attacker hosts a page at docs.apify.com.evil.com containing LLM instructions. When the tool fetches and returns this content, the LLM may follow the injected instructions. Security boundary violation: The allowlist was explicitly designed to restrict fetching to trusted documentation domains. The bypass defeats this intent. SSRF (limited): The tool can fetch from attacker-controlled servers, though the primary risk is the content returned to the LLM rather than network access.
Upgrade @apify/actors-mcp-server to 0.9.21 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.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @apify/actors-mcp-server | npm | < 0.9.21 | 0.9.21 |
1 registered MCP server installs an affected version today, by the dependency versions a fresh install resolves.
- io.github.cybairfly/codify-mcp@apify/actors-mcp-server@0.7.4
- 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
- HighApify Model Context Protocol (MCP) server: Actor MCP path authority injection leaks Apify token@apify/actors-mcp-server
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.