Approved changes feed: RSS · Atom

cpe:2.3:a:langchain:langchain_community:*:*:*:*:*:node.js:*:*

part: a version: * update: *

VendorLangchain (3bec1db6-30f1-5f7c-8067-d161076b8e16)
ProductLangchain Community (b605f601-9040-5dca-831b-ca027e98fe92)
Edition*
Language*
Software edition*
Target softwarenode.js
Target hardware*
Other*
NotesImported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
No PURL mappings for this CPE yet.

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-27795 vulnerable 2026-06-08 07:55:13.895851 LangChain Community: redirect chaining can lead to SSRF bypass via RecursiveUrlLoader
MEDIUM (4.1)
LangChain is a framework for building LLM-powered applications. Prior to version 1.1.8, a 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). Users should upgrade to `@langchain/community` 1.1.18, which validates every redirect hop by disabling automatic redirects and re-validating `Location` targets before following them. In this version, automatic redirects are disabled (`redirect: "manual"`), each 3xx `Location` is resolved and validated with `validateSafeUrl()` before the next request, and a maximum redirect limit prevents infinite loops.
Published: 2026-02-25T17:30:01.106Z
Updated: 2026-02-25T18:42:52.277Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2026-26019 vulnerable 2026-06-08 07:53:20.729683 @langchain/community affected by SSRF Bypass in RecursiveUrlLoader via insufficient URL origin validation
MEDIUM (4.1)
LangChain is a framework for building LLM-powered applications. Prior to 1.1.14, the RecursiveUrlLoader class in @langchain/community is a web crawler that recursively follows links from a starting URL. Its preventOutside option (enabled by default) is intended to restrict crawling to the same site as the base URL. The implementation used String.startsWith() to compare URLs, which does not perform semantic URL validation. An attacker who controls content on a crawled page could include links to domains that share a string prefix with the target, causing the crawler to follow links to attacker-controlled or internal infrastructure. Additionally, the crawler performed no validation against private or reserved IP addresses. A crawled page could include links targeting cloud metadata services, localhost, or RFC 1918 addresses, and the crawler would fetch them without restriction. This vulnerability is fixed in 1.1.14.
Published: 2026-02-11T21:11:10.166Z
Updated: 2026-02-12T21:14:41.756Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.