@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
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.
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.
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.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| @langchain/community | npm | <= 1.1.13 | 1.1.14 |
- CriticalMLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebindingmlflowExploited
- Critical@zereight/mcp-gitlab Vulnerable to Server-Side Request Forgery@zereight/mcp-gitlab
- CriticalSSRF + LLM API key exfiltration via user-controlled basepath / baseUrl in 8 chat-model nodesflowise, flowise-components
- CriticalLocalAI POST /models/apply permits unauthenticated server-side request forgery through gallery URLsgithub.com/mudler/LocalAI
- CriticalFastMCP OpenAPI Provider has an SSRF & Path Traversal Vulnerabilityfastmcp
- CriticalBentoML SSRF Vulnerability in File Upload Processingbentoml
- MediumLangChain Community: redirect chaining can lead to SSRF bypass via RecursiveUrlLoader@langchain/community
- Low@langchain/community SQL Injection vulnerability@langchain/community
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.