Quick answers
- Is CVE-2026-27795 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-27795 being exploited in the wild.
- How severe is CVE-2026-27795?
- Low severity, with a CVSS score of 3.1, published 25 February 2026.
- Which products and versions are affected?
- @langchain/community (npm) SEMVER:introduced=0,fixed=1.1.18.
- Is there a fix for CVE-2026-27795?
- Yes. @langchain/community (npm): upgrade to 1.1.18 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-27795 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-27795?
- 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.18 or later
npm install @langchain/community@1.1.18
Technical details
The vulnerability is a Server-Side Request Forgery (SSRF) bypass in RecursiveUrlLoader that exploits automatic redirect following. The component validates the initial URL against a blocklist (private IPs, cloud metadata endpoints) but does not re-validate when HTTP 3xx redirects are followed. An attacker can supply a URL that passes initial validation, which then redirects to a blocked destination (e.g., 169.254.169.254 for AWS metadata), and the underlying fetch() call follows the redirect without triggering the SSRF checks. This is a "check-then-act" gap: validation occurs before redirect resolution. The fix disables automatic redirects (redirect: "manual"), manually validates each Location header before following it, and enforces a maximum redirect limit. Affected versions: @langchain/community <= 1.1.17; patched in 1.1.18.
Affected products
- LangChain @langchain/community < 1.1.18
Identifiers
- CVE-2026-27795
- GHSA-mphv-75cg-56wg
Timeline
- 2026-02-25: disclosed
- 2026-02-25: patched: Version 1.1.18 released with fix