CVE-2026-41481 langchain-ai CVE debrief

Who should care

Developers and administrators using LangChain Text Splitters prior to version 1.1.2 should be aware of this SSRF vulnerability. Applications that expose Document contents or derivatives back to the requester who supplied the URL are at risk of sensitive data leakage from internal endpoints. Users of LangChain Text Splitters should assess their applications' exposure and update to version 1.1.2 or later to mitigate this vulnerability.

Technical summary

The `HTMLHeaderTextSplitter.split_text_from_url()` function in LangChain Text Splitters prior to version 1.1.2 is vulnerable to Server-Side Request Forgery (SSRF). The function validates the initial URL using `validate_safe_url()` but then performs the fetch with `requests.get()` with redirects enabled by default. This allows an attacker to bypass SSRF protections by redirecting to internal, localhost, or cloud metadata endpoints. The response body is parsed and returned as Document objects to the application code. The vulnerability's impact depends on how the application handles Document contents. This issue is addressed in version 1.1.2.

Defensive priority

Medium priority should be given to updating LangChain Text Splitters to version 1.1.2 or later due to the potential for SSRF and data leakage. Applications that expose Document contents to requesters are at higher risk and should be prioritized for mitigation.

Recommended defensive actions

• Update LangChain Text Splitters to version 1.1.2 or later.
• Assess applications using LangChain Text Splitters for exposure to Document content leakage.
• Implement additional SSRF protections for internal endpoints if updating is not immediately feasible.
• Monitor for suspicious activity related to LangChain Text Splitters usage.
• Review application code for secure handling of Document objects and derivatives.

Evidence notes

The CVE-2026-41481 vulnerability is documented in the official CVE record and NVD detail pages. The vulnerability was publicly disclosed on April 24, 2026, and last modified on June 30, 2026. Multiple sources, including GitHub security advisories and Red Hat security bulletins, provide additional context and mitigation guidance. The LangChain community has addressed this issue in version 1.1.2 of LangChain Text Splitters.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.