CVE-2026-50143Public exploitNetwork attack vector

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.

CVSS severity8.1
High
EPSS probability0.34%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

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

  1. Aug 18, 2026CVE publishedPublication date reported by the CVE source.
  2. 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.

  1. Affected versionversion=< 0.10.11

What conditions does exploitation require?

Attack vectornetwork
Required privilegesUnavailable in this record.

What is affected?

Apify · Apify MCP Serverversion=< 0.10.11

Published CVSS scores

8.1GitHub Advisory DatabaseCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

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.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-918Server-Side Request Forgery (SSRF)
CAPEC-664Server Side Request Forgery
T1528Steal Application Access Token

Public exploit references

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