CVE-2026-50143: Apify MCP Server Leaks API Tokens via Path Injection
CVE-2026-50143 is a high-severity credential theft issue (CVSS 8.1) in @apify/actors-mcp-server, a MCP server. Affected: <0.10.11. Fixed in 0.10.11.
Is @apify/actors-mcp-server running on your developers' machines? Anomity finds every device with this MCP server installed, shows the version, and can block it by policy. Detect this across your developers' devices with Anomity →
Key facts
- ID
CVE-2026-50143- Severity
- high
- CVSS score
- 8.1
- Attack type
- Credential theft
- Component
- @apify/actors-mcp-server · MCP server
- Package
@apify/actors-mcp-servernpm- Known exploited
- No known exploitation
- Published
- Last verified
What is CVE-2026-50143?
A path injection flaw in the @apify/actors-mcp-server npm package lets a malicious Actor with a crafted webServerMcpPath redirect the MCP client to an attacker host, exfiltrating the victim's Apify API token through the authorization header. Rated CVSS 8.1; any MCP client wired to a compromised Apify Actor is affected.
Affected versions
| Affected | Fixed in |
|---|---|
<0.10.11 | 0.10.11 |
Am I affected by CVE-2026-50143?
You are affected if you run @apify/actors-mcp-server <0.10.11. Versions 0.10.11 and later include the fix.
How do I fix CVE-2026-50143?
Upgrade @apify/actors-mcp-server to 0.10.11 or later to stop Apify token exfiltration via crafted MCP paths.
How do I find every machine running @apify/actors-mcp-server?
Anomity inventories the AI agents, MCP servers, IDE extensions and skills on each developer device, so you can see which machines run @apify/actors-mcp-server and which version, then enforce a policy on it.