Apify token exposure via authority injection
Published Aug 18, 2026 · Updated Aug 18, 2026
SSRF in Apify MCP Server before 0.10.11 allows attackers to expose an Apify API token via a malicious Actor definition. getActorMCPServerURL in src/mcp/actors.ts appends the attacker-controlled webServerMcpPath to a trusted standby URL without resolving and enforcing the resulting origin, so a userinfo-style authority value can redirect connectMCPClient to an attacker host that receives the Authorization bearer token. Exploitation requires a victim to invoke or inspect the malicious Actor through the call-actor, fetch-actor-details, or actor-mcp tool-loading paths, after which the stolen token can be used to access Actors, stored data, and billable compute.
Summary
What happened
SSRF in Apify MCP Server before 0.10.11 allows attackers to expose an Apify API token via a malicious Actor definition. getActorMCPServerURL in src/mcp/actors.ts appends the attacker-controlled webServerMcpPath to a trusted standby URL without resolving and enforcing the resulting origin, so a userinfo-style authority value can redirect connectMCPClient to an attacker host that receives the Authorization bearer token. Exploitation requires a victim to invoke or inspect the malicious Actor through the call-actor, fetch-actor-details, or actor-mcp tool-loading paths, after which the stolen token can be used to access Actors, stored data, and billable compute.
The record
- CVE
- CVE-2026-50143
- Published
- Aug 18, 2026
- Updated
- Aug 18, 2026
- Vendor
- Apify
- Product
- Apify MCP Server
- Classifications
- CWE-918, CAPEC-664, T1528
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.10.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-6gr2-qh89-hxwm proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo