# CVE-2026-41481: LangChain: HTMLHeaderTextSplitter.split_text_from_url SSRF Redirect Bypass

> Attackers can bypass SSRF protections in LangChain's HTMLHeaderTextSplitter to access internal endpoints via redirect bypass, potentially leaking sensitive data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Apr 2026
- **Updated:** 15 Jul 2026
- **Also known as:** CLEANSTART-2026-VO66326, CLEANSTART-2026-VS88264, CLSA-2026-1779670108, ECHO-2692-dd04-73d6, GHSA-fv5p-p927-qmxr, PYSEC-2026-77, ROOT-APP-PYPI-CVE-2026-41481, ROOT-APP-PYPI-GHSA-fv5p-p927-qmxr

## What is CVE-2026-41481?

CVE-2026-41481 is a medium-severity server-side request forgery vulnerability in langchain-ai langchain-text-splitters, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

LangChain is a framework for building agents and LLM-powered applications. Prior to langchain-text-splitters
 1.1.2, HTMLHeaderTextSplitter.split_text_from_url() validated the initial URL using validate_safe_url() but then performed the fetch with requests.get() with redirects enabled (the default). Because redirect targets were not revalidated, a URL pointing to an attacker-controlled server could redirect to internal, localhost, or cloud metadata endpoints, bypassing SSRF protections. The response body is parsed and returned as Document objects to the calling application code. Whether this constitutes a data exfiltration path depends on the application: if it exposes Document contents (or derivatives) back to the requester who supplied the URL, sensitive data from internal endpoints could be leaked. Applications that store or process Documents internally without returning raw content to the requester are not directly exposed to data exfiltration through this issue. This vulnerability is fixed in 1.1.2.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-41481?

3 open source packages ship an affected version, including langchain-text-splitters. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `langchain-text-splitters` | PyPI | All versions | 1.1.2 |
| `langchain-text-splitters` | PyPI | All versions | 1.1.2 |
| `langchain-text-splitters` | PyPI | All versions | 1.1.2 |

Products: Langchain Langchain-Text-Splitters.

## How do I fix CVE-2026-41481?

Upgrade langchain-text-splitters to 1.1.2 or later.

## Is CVE-2026-41481 being exploited?

There is no known exploitation of CVE-2026-41481 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41481 and fix it if it is affected.

What it is: CVE-2026-41481 is a medium-severity server-side request forgery vulnerability in langchain-ai langchain-text-splitters, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-41481 in the wild and no public exploit code.

Affected packages and fixed versions:
- langchain-text-splitters (PyPI): affected all versions; fixed in 1.1.2
- langchain-text-splitters (PyPI): affected all versions; fixed in 1.1.2
- langchain-text-splitters (PyPI): affected all versions; fixed in 1.1.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41481/ (Markdown: https://insights.sbomify.com/CVE-2026-41481/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41481
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41481
- OSV: https://osv.dev/vulnerability/CVE-2026-41481

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41481/
Summaries are generated and may contain mistakes; the official description above is the record.