langchain-ai helm up to 0.12.70 injection

Summaryinfo

A vulnerability was found in langchain-ai helm up to 0.12.70. It has been declared as problematic. Affected by this issue is some unknown functionality. Executing a manipulation can lead to injection. The identification of this vulnerability is CVE-2026-25750. The attack may be launched remotely. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability has been found in langchain-ai helm up to 0.12.70 and classified as critical. This vulnerability affects some unknown processing. The manipulation with an unknown input leads to a injection vulnerability. The CWE definition for the vulnerability is CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability was named CVE-2026-25750 since 02/05/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1055.

Upgrading to version 0.12.71 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Artificial Intelligence Software

Vendor

• langchain-ai

Name

• helm

Version

• 0.12.0
• 0.12.1
• 0.12.2
• 0.12.3
• 0.12.4
• 0.12.5
• 0.12.6
• 0.12.7
• 0.12.8
• 0.12.9
• 0.12.10
• 0.12.11
• 0.12.12
• 0.12.13
• 0.12.14
• 0.12.15
• 0.12.16
• 0.12.17
• 0.12.18
• 0.12.19
• 0.12.20
• 0.12.21
• 0.12.22
• 0.12.23
• 0.12.24
• 0.12.25
• 0.12.26
• 0.12.27
• 0.12.28
• 0.12.29
• 0.12.30
• 0.12.31
• 0.12.32
• 0.12.33
• 0.12.34
• 0.12.35
• 0.12.36
• 0.12.37
• 0.12.38
• 0.12.39
• 0.12.40
• 0.12.41
• 0.12.42
• 0.12.43
• 0.12.44
• 0.12.45
• 0.12.46
• 0.12.47
• 0.12.48
• 0.12.49
• 0.12.50
• 0.12.51
• 0.12.52
• 0.12.53
• 0.12.54
• 0.12.55
• 0.12.56
• 0.12.57
• 0.12.58
• 0.12.59
• 0.12.60
• 0.12.61
• 0.12.62
• 0.12.63
• 0.12.64
• 0.12.65
• 0.12.66
• 0.12.67
• 0.12.68
• 0.12.69
• 0.12.70

Website

• Product: https://github.com/langchain-ai/helm/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion