dbcve.org
Langchain Text SplittersApplication · Langchain

CVE-2026-41481

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-24
Fix available
A fix is available. Upgrade to 1.1.2 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SSRF bypass via unvalidated HTTP redirects in langchain-text-splitters HTMLHeaderTextSplitter.split_text_from_url(). The function validates the initial URL but does not revalidate redirect targets, allowing attackers to redirect requests to internal, localhost, or cloud metadata endpoints (e.g., AWS169, GCP metadata). Data exfiltration occurs only if the application exposes Document contents (or derivatives) back to the URL requester.

MitigationUpgrade langchain-text-splitters to version 1.1.2 or later; additionally review application code to ensure Document content from fetched URLs is not returned to the requester.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Langchain Text SplittersApplication
Affected:< 1.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed version of langchain-text-splitters
    Run 'pip show langchain-text-splitters' or check your requirements.txt / pyproject.toml for the installed version
    Affected if The installed version is less than 1.1.2 (e.g., 1.1.0, 1.0.x, etc.)
  2. Identify usage of HTMLHeaderTextSplitter.split_text_from_url()
    Search your codebase for imports or usage of 'HTMLHeaderTextSplitter' and calls to 'split_text_from_url' method
    Affected if Your code calls HTMLHeaderTextSplitter.split_text_from_url() to fetch and parse content from URLs provided by users or external sources
  3. Verify if URL requester can receive Document content back
    Review application logic to determine if content fetched via split_text_from_url() is returned to the requester (e.g., API response, rendered page)
    Affected if The fetched URL content or its derivatives are exposed back to the original requester, enabling potential data exfiltration through crafted redirect targets
  4. Test for redirect validation gaps
    Provide a URL that redirects to an internal endpoint (e.g., http://169.254.169.254/latest/meta-data/) as input to split_text_from_url() and observe if the request reaches that internal endpoint
    Affected if The function follows redirects to internal/cloud metadata endpoints without validating the redirect target

You are affected if you use a langchain-text-splitters version below 1.1.2, call split_text_from_url() on untrusted URLs, and expose the fetched Document content back to the requester.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.1.2 or later
Fixed in 1.1.2
Interim mitigation

Upgrade langchain-text-splitters to version 1.1.2 or later; additionally review application code to ensure Document content from fetched URLs is not returned to the requester.

Recommended fix High confidence

langchain-text-splitters >= 1.1.2

  1. Check the current version of langchain-text-splitters installed (e.g., pip show langchain-text-splitters or pip list | grep langchain-text-splitters)
  2. Upgrade to version 1.1.2 or later using: pip install --upgrade langchain-text-splitters>=1.1.2
  3. Verify the upgrade was successful by checking the installed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Langchain Text Splitters Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41481 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41481 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data