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.
CVE-2026-50143
This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(medium)
- EG Risk
- 52(Track*)EG Risk 52/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity81% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 26%
- KEV
- Not listed
Published
July 1, 2026
Last Modified
August 18, 2026
Advisory Details (4)
Auto-updated Aug 18, 20260.10.11
Patch available: apify/apify-mcp-server v0.10.11
https://github.com/apify/apify-mcp-server/releases/tag/v0.10.11commit ef686d77da3d (apify/apify-mcp-server)
Patch available: apify/apify-mcp-server v0.10.11 (contains commit ef686d77da3d)
https://github.com/apify/apify-mcp-server/commit/ef686d77da3d3c86c30b2ae24218d756aa38e09cfix(mcp): Validate webServerMcpPath stays within Actor standby origin
Patch available: apify/apify-mcp-server v0.10.11 (PR #927 merged 2026-05-28)
https://github.com/apify/apify-mcp-server/pull/927Actor MCP path authority injection leaks Apify token · Advisory · apify/apify-mcp-server · GitHub
https://github.com/apify/apify-mcp-server/security/advisories/GHSA-6gr2-qh89-hxwmVendor Advisories for CVE-2026-50143(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @apify/actors-mcp-server | — | 0.10.11 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 17× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 16:15 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 20:58 UTCEG score recompute
- 2026-08-23 07:01 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 06:54 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 04:30 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 04:35 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 07:41 UTCEG score recompute
- 2026-08-18 20:25 UTCEG score recompute
- 2026-08-18 19:45 UTCEG score recompute
- 2026-08-18 18:25 UTCEG score recompute
- 2026-07-30 11:03 UTCEG score recompute
- 2026-07-26 13:13 UTCEG score recompute
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-01 23:02 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-918
- CVE-2016-10927EG 10.0CRITICAL
- CVE-2016-10926EG 10.0CRITICAL
- CVE-2018-10511EG 10.0CRITICAL
- CVE-2018-1000124EG 10.0CRITICAL
- CVE-2017-11291EG 10.0EPSS p92CRITICAL
- CVE-2017-12905EG 10.0CRITICAL
- CVE-2017-8794EG 10.0CRITICAL
- CVE-2017-13667EG 9.9CRITICAL
- CVE-2017-17674EG 9.8CRITICAL
- CVE-2013-4864EG 9.8EPSS p93CRITICAL
Frequently asked(5)
What is CVE-2026-50143?
When was CVE-2026-50143 disclosed?
Is CVE-2026-50143 actively exploited?
What is the CVSS score of CVE-2026-50143?
How do I remediate CVE-2026-50143?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50143
Is Your Infrastructure Affected by CVE-2026-50143?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.