Skip to main content
VulnerabilityPublished

CVE-2026-25750: langchain-ai helm · Injection

Affects langchain-ai helmSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.5 High : upgrade to 0.12.71 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.12.71
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade helm and langchain-ai/helm to 0.12.71.

Affected software

ProductAffectedFixed in
langchain-aihelmAffected
  • <0.12.71
Fixed in
  • 0.12.71
GitHublangchain-ai/helmpkg:github/langchain-ai/helmOther threatsAffected
  • <0.12.71
Fixed in
  • 0.12.71

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade all Langchain Helm Chart deployments to version 0.12.71 or later, which includes the fix enforcing allowed origins validation on the baseUrl parameter. For self-hosted customers, immediate patching is critical as no workarounds exist. Organizations should also implement robust phishing awareness training to reduce the likelihood of users clicking malicious links. Network-level protections such as URL filtering and email security gateways can help block known malicious URLs. Monitoring for unusual access patterns or repeated authentication token usage may help detect exploitation attempts. Where possible, enforce short session lifetimes and multi-factor authentication to reduce the impact of stolen tokens. Additionally, review and restrict user permissions within LangSmith workspaces to limit potential damage from compromised accounts. Finally, maintain up-to-date inventories of affected deployments to ensure comprehensive patch management.

Description

Langchain Helm Charts are Helm charts for deploying Langchain applications on Kubernetes. Prior to langchain-ai/helm version 0.12.71, a URL parameter injection vulnerability existed in LangSmith Studio that could allow unauthorized access to user accounts through stolen authentication tokens. The vulnerability affected both LangSmith Cloud and self-hosted deployments. Authenticated LangSmith users who clicked on a specially crafted malicious link would have their bearer token, user ID, and workspace ID transmitted to an attacker-controlled server. With this stolen token, an attacker could impersonate the victim and access any LangSmith resources or perform any actions the user was authorized to perform within their workspace. The attack required social engineering (phishing, malicious links in emails or chat applications) to convince users to click the crafted URL. The stolen tokens expired after 5 minutes, though repeated attacks against the same user were possible if they could be convinced to click malicious links multiple times. The fix in version 0.12.71 implements validation requiring user-defined allowed origins for the baseUrl parameter, preventing tokens from being sent to unauthorized servers. No known workarounds are available. Self-hosted customers must upgrade to the patched version.

References

Community reviews

Loading reviews…