CVE-2026-41481 Vulnerability Analysis & Exploit Details

CVE-2026-41481
Vulnerability Scoring

6.5
/10
High Risk

If left unpatched, CVE-2026-41481 could lead to major system disruptions or data loss.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2026-41481 Details

Status: Analyzed

Last updated: 🕞 28 Apr 2026, 15:43 UTC
Originally published on: 🕘 24 Apr 2026, 21:16 UTC

Time between publication and last update: 3 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2026-41481 Vulnerability Summary

CVE-2026-41481: 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.

Assessing the Risk of CVE-2026-41481

Access Complexity Graph

The exploitability of CVE-2026-41481 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-41481

With low attack complexity and no required privileges, CVE-2026-41481 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-41481, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-41481, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-41481 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2026-41481 poses no threat to data integrity.
  • Availability: None
    CVE-2026-41481 does not impact system availability.

CVE-2026-41481 References

External References

CWE Common Weakness Enumeration

CWE-918

CAPEC Common Attack Pattern Enumeration and Classification

  • Server Side Request Forgery CAPEC-664 An adversary exploits improper input validation by submitting maliciously crafted input to a target application running on a server, with the goal of forcing the server to make a request either to itself, to web services running in the server’s internal network, or to external third parties. If successful, the adversary’s request will be made with the server’s privilege level, bypassing its authentication controls. This ultimately allows the adversary to access sensitive data, execute commands on the server’s network, and make external requests with the stolen identity of the server. Server Side Request Forgery attacks differ from Cross Site Request Forgery attacks in that they target the server itself, whereas CSRF attacks exploit an insecure user authentication mechanism to perform unauthorized actions on the user's behalf.

Vulnerable Configurations

  • cpe:2.3:a:langchain:langchain-text-splitters:0.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.3.4:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.3.4:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.3.5:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.3.5:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.3.6:-:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.3.6:-:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.3.6:rc1:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.3.6:rc1:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.3.7:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.3.7:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.3.8:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.3.8:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.3.9:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.3.9:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.3.10:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.3.10:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:0.3.11:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:0.3.11:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:1.0.0:-:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:1.0.0:-:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:1.0.0:a1:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:1.0.0:a1:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:langchain:langchain-text-splitters:1.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:langchain:langchain-text-splitters:1.1.1:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-41481: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-8328 – The ftpcp() function in Lib/ftplib.py was not updated when CVE-2021-4189 was fixed. While makepasv() was patched to replace server-supplied PASV ...
  • CVE-2026-45714 – CubeCart is an ecommerce software solution. Prior to 6.7.0, an Authenticated Server-Side Template Injection (SSTI) vulnerability exists in multiple...
  • CVE-2026-45708 – CubeCart is an ecommerce software solution. Prior to 6.7.3, an admin with documents edit permission can save raw <?php … ?> into the Invoice Editor...
  • CVE-2026-45229 – Quark Drive before 0.8.5 contains a mass assignment vulnerability in the POST /update endpoint that allows authenticated attackers to overwrite adm...
  • CVE-2026-45228 – Quark Drive before 0.8.5 contains a stored cross-site scripting vulnerability in the System Configuration page where the template renders push_conf...