CVE-2026-50143

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

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 computed
Severity81% × 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, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

0.10.11

Patch available: apify/apify-mcp-server v0.10.11

https://github.com/apify/apify-mcp-server/releases/tag/v0.10.11
github_commit Patch Available

commit 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/ef686d77da3d3c86c30b2ae24218d756aa38e09c
github_pr Patch Available

fix(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/927
github Patch Available🟡 PoC Available

Actor 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-hxwm

Vendor 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)
PackageVulnerable rangeFixed inDependents
@apify/actors-mcp-server0.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.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 16:15 UTCEG score recompute
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-24 20:58 UTCEG score recompute
  5. 2026-08-23 07:01 UTCEG score recompute
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 06:54 UTCEG score recompute
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-21 04:30 UTCEG score recompute
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-20 04:35 UTCEG score recompute
  12. 2026-08-19 17:04 UTCEPSS rescore
  13. 2026-08-19 07:41 UTCEG score recompute
  14. 2026-08-18 20:25 UTCEG score recompute
  15. 2026-08-18 19:45 UTCEG score recompute
  16. 2026-08-18 18:25 UTCEG score recompute
  17. 2026-07-30 11:03 UTCEG score recompute
  18. 2026-07-26 13:13 UTCEG score recompute
  19. 2026-07-23 03:18 UTCEG score recompute
  20. 2026-07-01 23:02 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-50143?
CVE-2026-50143 is a high vulnerability published on July 1, 2026. 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…
When was CVE-2026-50143 disclosed?
CVE-2026-50143 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50143 actively exploited?
CVE-2026-50143 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 73.7% of all scored CVEs.
What is the CVSS score of CVE-2026-50143?
CVE-2026-50143 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-50143?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50143, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-50143

Explore →

Is Your Infrastructure Affected by CVE-2026-50143?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.