CVE-2026-50143
Description
The Apify MCP server enables AI agents to extract data from websites using ready-made scrapers, crawlers, and automation tools available on the Apify Store. Prior to 0.10.11, getActorMCPServerURL in src/mcp/actors.ts concatenates the trusted Actor standby URL with the attacker-controlled webServerMcpPath from an Actor definition without verifying the resulting origin, allowing a malicious Actor publisher to use a userinfo-style authority value to redirect connectMCPClient to a third-party host. The call-actor, fetch-actor-details, and actor-mcp tool-loading paths pass this URL to transports in src/mcp/client.ts that attach the victim Authorization bearer token, exposing the Apify API token and enabling access to Actors, stored data, and billable compute. A victim must invoke or inspect the attacker-controlled Actor. This issue is fixed in version 0.10.11.
References
- https://github.com/apify/apify-mcp-server/commit/ef686d77da3d3c86c30b2ae24218d756aa38e09c
- https://github.com/apify/apify-mcp-server/pull/927
- https://github.com/apify/apify-mcp-server/releases/tag/v0.10.11
- https://github.com/apify/apify-mcp-server/security/advisories/GHSA-6gr2-qh89-hxwm
- https://github.com/apify/apify-mcp-server/security/advisories/GHSA-6gr2-qh89-hxwm