CVE-2026-27795: LangChain Community Redirect Chaining Can Lead To Vulnerability
MODERATECVE-2026-27795 is a MODERATE (CVSS 4.1) redirect chaining can lead to vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting LangChain Community libraries in the npm ecosystem. The issue involves redirect chaining can lead to ssrf bypass via recursiveurlloader. Remediation is available by upgrading affected packages to version 1.1.18.
CVE-2026-27795 at a Glance
Security Impact
CVSS: 4.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N).
How to Fix CVE-2026-27795
To remediate this vulnerability, upgrade all affected LangChain Community dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @langchain/community@1.1.18
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @langchain/community
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-27795, inspect your project dependencies using npm:
npm ls @langchain/community
Analyze the terminal output to locate any version of LangChain Community in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.1.18), your application is affected.
Note: The npm ls @langchain/community command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In LangChain Community, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-27795 Affected LangChain Community Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@langchain/community
|
npm |
< 1.1.18
|
1.1.18
|
References
Frequently Asked Questions
What is CVE-2026-27795?
Which LangChain Community versions are affected?
What version fixes CVE-2026-27795?
Is @langchain/community affected?
What is the CVSS score of CVE-2026-27795?
What CWE is associated with CVE-2026-27795?
How can I check npm dependencies for CVE-2026-27795?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-mphv-75cg-56wg",
"modified" : "2026-02-25T22:59:48Z",
"published" : "2026-02-25T22:59:48Z",
"aliases" : [ "CVE-2026-27795" ],
"summary" : "LangChain Community: redirect chaining can lead to SSRF bypass via RecursiveUrlLoader",
"details" : "## Summary\nA redirect-based Server-Side Request Forgery (SSRF) bypass exists in `RecursiveUrlLoader` in `@langchain/community`. The loader validates the initial URL but allows the underlying fetch to follow redirects automatically, which permits a transition from a safe public URL to an internal or metadata endpoint without revalidation. This is a bypass of the SSRF protections introduced in 1.1.14 (CVE-2026-26019).\n\n## Affected Component\n- Package: `@langchain/community`\n- Component: `RecursiveUrlLoader`\n- Configuration: `preventOutside` (default: `true`) is insufficient to prevent this bypass when redirects are followed automatically.\n\n## Description\n`RecursiveUrlLoader` is a web crawler that recursively follows links from a starting URL. The existing SSRF mitigation validates the initial URL before fetching, but it does not re-validate when the request follows redirects. Because fetch follows redirects by default, an attacker can supply a public URL that passes validation and then redirects to a private network address, localhost, or cloud metadata endpoint.\n\nThis constitutes a “check‑then‑act” gap in the request lifecycle: the safety check occurs before the redirect chain is resolved, and the final destination is never validated.\n\n## Impact\nIf an attacker can influence content on a page being crawled (e.g., user‑generated content, untrusted external pages), they can cause the crawler to:\n- Fetch cloud instance metadata (AWS, GCP, Azure), potentially exposing credentials or tokens\n- Access internal services on private networks (`10.x`, `172.16.x`, `192.168.x`)\n- Connect to localhost services\n- Exfiltrate response data through attacker-controlled redirect chains\n\nThis is exploitable in any environment where `RecursiveUrlLoader` runs with access to internal networks or metadata services, which includes most cloud-hosted deployments.\n\n## Attack Scenario\n1. The crawler is pointed at a public URL that passes initial SSRF validation.\n2. That URL responds with a 3xx redirect to an internal target.\n3. The fetch follows the redirect automatically without revalidation.\n4. The crawler accesses the internal or metadata endpoint.\n\nExample redirector:\n```\nhttps://302.r3dir.me/--to/?url=http://169.254.169.254/latest/meta-data/\n```\n\n## Root Cause\n- SSRF validation (`validateSafeUrl`) is only performed on the initial URL.\n- Redirects are followed automatically by fetch (`redirect: \"follow\"` default), so the request can change destinations without additional validation.\n\n## Resolution\nUpgrade to `@langchain/community` **>= 1.1.18**, which validates every redirect hop by disabling automatic redirects and re-validating `Location` targets before following them.\n- Automatic redirects are disabled (`redirect: \"manual\"`).\n- Each 3xx `Location` is resolved and validated with `validateSafeUrl()` before the next request.\n- A maximum redirect limit prevents infinite loops.\n\n## Reources\n- Original SSRF fix (CVE-2026-26019): enforced origin comparison and added initial URL validation\n- https://github.com/langchain-ai/langchainjs/security/advisories/GHSA-gf3v-fwqg-4vh7",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@langchain/community"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.1.18"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.1.17"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/langchain-ai/langchainjs/security/advisories/GHSA-gf3v-fwqg-4vh7"
}, {
"type" : "WEB",
"url" : "https://github.com/langchain-ai/langchainjs/security/advisories/GHSA-mphv-75cg-56wg"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-27795"
}, {
"type" : "WEB",
"url" : "https://github.com/langchain-ai/langchainjs/pull/9990"
}, {
"type" : "WEB",
"url" : "https://github.com/langchain-ai/langchainjs/commit/2812d2b2b9fd9343c4850e2ab906b8cf440975ee"
}, {
"type" : "WEB",
"url" : "https://github.com/langchain-ai/langchainjs/commit/d5e3db0d01ab321ec70a875805b2f74aefdadf9d"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/langchain-ai/langchainjs"
}, {
"type" : "WEB",
"url" : "https://github.com/langchain-ai/langchainjs/releases/tag/%40langchain%2Fcommunity%401.1.14"
}, {
"type" : "WEB",
"url" : "https://github.com/langchain-ai/langchainjs/releases/tag/%40langchain%2Fcommunity%401.1.18"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-918" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-02-25T22:59:48Z",
"nvd_published_at" : "2026-02-25T18:23:41Z"
}
}