dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-59152

MEDIUM · 5.0 CVSS v3.1 Published 2026-07-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
LangSmith Client SDKs provide SDK's for interacting with the LangSmith platform. Prior to 0.8.18, an attacker who can send an HTTP request to a server running the LangSmith SDK's TracingMiddleware can cause that server to read an arbitrary file from its local filesystem and upload the contents to LangSmith as a trace attachment. Depending on how the distributed trace system is deployed, triggering a read may not require authentication. Retrieving the contents requires read access to the LangSmith workspace the traces are sent to. The net effect is a trust-boundary crossing: a party with workspace trace-read access (for example a low-privilege workspace member, a contractor, or a compromised teammate account) gains the ability to read files from any server running TracingMiddleware, a capability outside that workspace's intended trust boundary. This vulnerability is fixed in 0.8.18.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In LangSmith Client SDKs prior to 0.8.18, the TracingMiddleware contains a file read vulnerability allowing an attacker with workspace trace-read access to send crafted HTTP requests that cause the server to read arbitrary local files and upload them to LangSmith as trace attachments. This represents a trust-boundary crossing where a low-privilege workspace member can access files from servers running the middleware.

MitigationUpgrade LangSmith Client SDKs to version 0.8.18 or later. Additionally, audit which servers run TracingMiddleware and review access controls on LangSmith workspaces.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed LangSmith Client SDK version
    Run 'pip show langsmith' or check your package manager for the installed langsmith package version
    Affected if The version listed is lower than 0.8.18
  2. Locate TracingMiddleware configuration
    Search your codebase and configuration files for 'TracingMiddleware' or trace middleware setup code that initializes LangSmith client
    Affected if TracingMiddleware is actively configured or imported in your application
  3. Verify trace data processing from workspace users
    Review whether your LangSmith workspace accepts trace data from users who have trace-read access but are not trusted administrators
    Affected if Low-privilege workspace members can submit trace data to your LangSmith workspace
  4. Check for sensitive file exposure
    Inspect recent LangSmith trace attachments in your workspace for any unexpected files that were uploaded as trace artifacts
    Affected if Any trace attachment contains files from your server filesystem that were not intentionally uploaded

Your environment is affected if you run a LangSmith Client SDK version below 0.8.18 with TracingMiddleware enabled and your workspace allows trace submissions from users with limited access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade LangSmith Client SDKs to version 0.8.18 or later. Additionally, audit which servers run TracingMiddleware and review access controls on LangSmith workspaces.

Recommended fix High confidence

0.8.18

  1. Identify all servers and applications running LangSmith Client SDK with TracingMiddleware enabled
  2. Check the current installed version of the LangSmith Client SDK (e.g., pip show langsmith or package.json dependency)
  3. Upgrade the LangSmith Client SDK to version 0.8.18 or later using your package manager (e.g., pip install langsmith>=0.8.18 or npm install langsmith@latest)
  4. After upgrading, verify the new version is correctly installed
  5. Restart any services running TracingMiddleware to ensure the updated SDK is loaded
  6. Test that the application functions normally with the updated SDK

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-59152 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-59152 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data