Is CVE-2026-26019 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-26019 being exploited in the wild.

How severe is CVE-2026-26019?

Low severity, with a CVSS score of 3.1, published 11 February 2026.

Which products and versions are affected?

@langchain/community (npm) SEMVER:introduced=0,fixed=1.1.14.

Is there a fix for CVE-2026-26019?

Yes. @langchain/community (npm): upgrade to 1.1.14 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-26019 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-26019?

Check whether you run @langchain/community (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-26019: LangChain @langchain/community SSRF bypass in RecursiveUrlLoader

CVE-2026-26019 · Severity: low · CVSS 3.1 · Published 2026-02-11

The @langchain/community web crawler library contains a flaw that allows attackers to bypass origin validation, enabling the crawler to access internal cloud metadata services and private network resources. An attacker who controls content on a crawled page can inject links that trick the crawler into fetching sensitive cloud credentials or connecting to internal infrastructure, potentially exposing IAM tokens, session credentials, and other sensitive data.

Technologies: @langchain/community (npm). Vendors: npm.

Quick answers

Is CVE-2026-26019 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-26019 being exploited in the wild.
How severe is CVE-2026-26019?: Low severity, with a CVSS score of 3.1, published 11 February 2026.
Which products and versions are affected?: @langchain/community (npm) SEMVER:introduced=0,fixed=1.1.14.
Is there a fix for CVE-2026-26019?: Yes. @langchain/community (npm): upgrade to 1.1.14 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-26019 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-26019?: Check whether you run @langchain/community (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

@langchain/community (npm): upgrade to 1.1.14 or later
```
npm install @langchain/community@1.1.14
```

Technical details

The vulnerability is a Server-Side Request Forgery (SSRF) bypass in the RecursiveUrlLoader class caused by two insufficient validation mechanisms: (1) the preventOutside origin check used String.startsWith() instead of semantic URL validation, allowing bypass via string-prefix-matching domains (e.g., https://example.com.attacker.com bypasses a check against https://example.com), and (2) no validation against private/reserved IP ranges or cloud metadata endpoints. An attacker who controls content on a crawled page (via user-generated content, public forums, or compromised sites) can inject links targeting 169.254.169.254, localhost, or RFC 1918 addresses, causing the crawler to fetch them without restriction. The fix replaces string comparison with strict origin validation using the URL API and introduces SSRF validation that blocks cloud metadata endpoints, private IP ranges, and non-HTTP schemes. Patch available in version 1.1.14.

Affected products

LangChain @langchain/community <= 1.1.13

Identifiers

CVE-2026-26019
GHSA-gf3v-fwqg-4vh7

Timeline

2026-02-11: disclosed
2026-02-11: patched: Version 1.1.14

References

https://github.com/langchain-ai/langchainjs/security/advisories/GHSA-gf3v-fwqg-4vh7

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.