SSRF (Server-Side Request Forgery) in @apify/actors-mcp-server (CVE-2026-50143)
Summary
SSRF in @apify/actors-mcp-server (CVE-2026-50143). Confidential information can be exposed externally. Exploitable via webServerMcpPath. Mitigation: upgrade to 0.10.11 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-50143 has been found in @apify/actors-mcp-server.
Attackers can target a specific entry point like webServerMcpPath over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade @apify/actors-mcp-server to 0.10.11 or later.
If unsure, ask your IT team or search "@apify/actors-mcp-server CVE-2026-50143" on the vendor's site.
CVE-2026-50143 (@apify/actors-mcp-server) — CWE-918 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: webServerMcpPath / mcpServerPath / standbyUrl / attacker.example
Patched: 0.10.11 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in @apify/actors-mcp-server. Attackers reach the vulnerable code path via webServerMcpPath without authentication.
Check the vendor advisory for the affected versions of @apify/actors-mcp-server. Attack surface: webServerMcpPath / mcpServerPath / standbyUrl / attacker.example.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 0.10.11.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@apify/actors-mcp-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@apify/actors-mcp-server' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@apify/actors-mcp-serverを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @apify/actors-mcp-server to 0.10.11ステージング環境で 0.10.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com