Apify apify-mcp-server
Actor MCP path authority injection leaks Apify token
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.10.11
Fixed in 0.10.11
Mitigation
Upgrade apify-mcp-server to 0.10.11 or later.
References
- Vendor advisory github.com/apify/apify-mcp-server/security/adv…
- Patch github.com/apify/apify-mcp-server/pull/927
- Patch github.com/apify/apify-mcp-server/commit/ef686…
1 more
- Release notes github.com/apify/apify-mcp-server/releases/tag…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.