cve.bz

CVE-2026-25528 langchain-ai langsmith-sdk: SSRF

5.8 mediumEPSS 0.3%Fix available

Medium (5.8) in langchain-ai langsmith-sdk. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in langsmith 0.4.6, 0.6.3.

On this page
LangSmith Client SDKs provide SDK's for interacting with the LangSmith platform. The LangSmith SDK's distributed tracing feature is vulnerable to Server-Side Request Forgery via malicious HTTP headers. An attacker can inject arbitrary api_url values through the baggage header, causing the SDK to exfiltrate sensitive trace data to attacker-controlled endpoints. When using distributed tracing, the SDK parses incoming HTTP headers via RunTree.from_headers() in Python or RunTree.fromHeaders() in Typescript. The baggage header can contain replica configurations including api_url and api_key fields. Prior to the fix, these attacker-controlled values were accepted without validation. When a traced operation completes, the SDK's post() and patch() methods send run data to all configured replica URLs, including any injected by an attacker. This vulnerability is fixed in version 0.6.3 of the Python SDK and 0.4.6 of the JavaScript SDK.

Severity

CVSS 3.1

5.8 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-02-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • langsmith (PyPI): fixed in 0.6.3
  • langsmith (npm): fixed in 0.4.6

Ask an AI about this CVE

Show the promptExplain CVE-2026-25528 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-25528?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-25528?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-25528 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
langchain-ai langsmith-sdk>= 0.4.10, <0.6.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-v34v-rq6j-cj6pPyPIlangsmith>=0.4.10 <0.6.30.6.3
GHSA-v34v-rq6j-cj6pnpmlangsmith>=0.3.41 <0.4.60.4.6
PYSEC-2026-2584PyPIlangsmith>=0.4.10 <0.6.30.6.3

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON