UTC
Medium

@langchain/community affected by SSRF Bypass in RecursiveUrlLoader via insufficient URL origin validation

CVE-2026-26019 · GHSA-gf3v-fwqg-4vh7 · published 2026-02-11 · updated 2026-02-12

Severity
Medium
CVSS score
4.1
Chance of exploitation (EPSS)
0.39%
Fixed in
1.1.14
  • Exploitation No known exploitation
  • Automatable No
  • Technical impact Partial
  • CISA SSVC
What it is

An attacker who can influence the content of a page being crawled (e.g., by placing a link on a public-facing page, forum, or user-generated content) could cause the crawler to: Fetch cloud instance metadata (AWS, GCP, Azure), potentially exposing IAM credentials and session tokens Access internal services on private networks (10.x, 172.16.x, 192.168.x) Connect to localhost services Exfiltrate response data via attacker-controlled redirect chains This is exploitable in any environment where RecursiveUrlLoader runs on infrastructure with access to cloud metadata or internal services — which includes most cloud-hosted deployments.

What to do

Upgrade @langchain/community to 1.1.14 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Two changes were made: 1. Origin comparison replaced. The startsWith check was replaced with a strict origin comparison using the URL API ( ). This correctly validates scheme, hostname, and port as a unit, preventing subdomain-based bypasses. 2. SSRF validation added to all fetch operations. A new URL validation module (@langchain/core/utils/ssrf) was introduced and applied before every outbound fetch in the crawler.

If you cannot upgrade yet

Users who cannot upgrade immediately should avoid using RecursiveUrlLoader on untrusted or user-influenced content, or should run the crawler in a network environment without access to cloud metadata or internal services.

Affected
PackageRegistryAffectedFixed in
@langchain/communitynpm<= 1.1.131.1.14

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].