CVE-2026-46341 is a medium-severity improper input validation vulnerability in @apify/actors-mcp-server (npm), affecting versions < 0.9.21. It is fixed in 0.9.21.
Summary The fetch-apify-docs tool validates URLs against a domain allowlist using String.startsWith() instead of proper URL hostname comparison. This allows bypass via attacker-controlled subdomains (e.g., https://docs.apify.com.evil.com/), enabling the tool to fetch and return arbitrary web content to the LLM. Details Vulnerable component src/tools/common/fetchapifydocs.ts, line 51: src/const.ts, lines 167-170: How the bypass works String.startsWith('https://docs.apify.com') matches any string beginning with that prefix, including: https://docs.apify.com.evil.com/payload - attacker-controlled subdomain https://[email protected]/payload - userinfo component in URL (browser behavior varies, but fetch() in Node.js may follow this) https://docs.apify.com.evil.com:8080/path - custom port on attacker domain All of these pass the startsWith check because they begin with the exact string https://docs.apify.com. The fetched content is returned to the LLM After the allowlist check passes, the tool fetches the URL and returns the full page content as markdown (fetchapifydocs.ts:69-103): The HTML is converted to markdown and returned verbatim to the LLM. This creates a prompt injection vector - the attacker's page can contain instructions that the LLM may follow. While tools like get-html-skeleton have no domain allowlist at all - it accepts any URL. The fetch-apify-docs tool was clearly intended to be more restricted (documentation-only), but the startsWith check defeats that intent. PoC The URL passes the startsWith('https://docs.apify.com') check, fetches the attacker's page, and returns its content to the LLM. Impact Prompt injection via fetched content: Attacker hosts a page at docs.apify.com.evil.com containing LLM instructions. When the tool fetches and returns this content, the LLM may follow the injected instructions. Security boundary violation: The allowlist was explicitly designed to restrict fetching to trusted documentation domains. The bypass defeats this intent. SSRF (limited): The tool can fetch from attacker-controlled servers, though the primary risk is the content returned to the LLM rather than network access. Account compromise via meta.apifyToken: Injected prompt instructions can direct the LLM to include a specific meta.apifyToken (the server's per-request token feature) in subsequent call-actor invocations, redirecting billable operations to a victim's account or accessing their private Actors
The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.
CVE-2026-46341 has a CVSS score of 6.1 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (0.9.21). Upgrading removes the vulnerable code path.
npm
@apify/actors-mcp-server (< 0.9.21)@apify/actors-mcp-server → 0.9.21 (npm)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-46341 is reachable in your applications. Explore AI application security for your team.
See if CVE-2026-46341 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-46341 in your environment →Upgrade @apify/actors-mcp-server to 0.9.21 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-46341 is a medium-severity improper input validation vulnerability in @apify/actors-mcp-server (npm), affecting versions < 0.9.21. It is fixed in 0.9.21. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
CVE-2026-46341 has a CVSS score of 6.1 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
@apify/actors-mcp-server (npm) versions < 0.9.21 is affected.
Yes. CVE-2026-46341 is fixed in 0.9.21. Upgrade to this version or later.
Whether CVE-2026-46341 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade @apify/actors-mcp-server to 0.9.21 or later.