Description
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.
Recommendation
Update the @langchain/community package to the latest compatible version. Followings are version details:
- Affected version(s): <= 1.1.17
- Patched version(s): 1.1.18
References
Could your website be exposed too?
SmartScanner can check your website for LangChain Community: redirect chaining can lead to SSRF bypass via RecursiveUrlLoader and gives you actionable findings to investigate.
Start a free scanRelated Issues
- @langchain/community affected by SSRF Bypass in RecursiveUrlLoader via insufficient URL origin validation - CVE-2026-26019
- Papra HTTP redirect bypass can lead to SSRF via webhook delivery system - CVE-2026-48051
- Axios: no_proxy bypass via IP alias allows SSRF - CVE-2026-42038
- nuxt-og-image SSRF — bypass of GHSA-pqhr-mp3f-hrpp / v6.2.5 fix (IPv6 + redirect) - CVE-2026-44589
You might also like:
See something that needs correcting? Let us knowUpdated February 25, 2026