GHSA-F4XH-W4CJ-QXQ8 is a high-severity path traversal vulnerability in langsmith (pip), affecting versions < 0.8.18. It is fixed in 0.8.18.
Summary 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. Impact Confidentiality (High): arbitrary read of files accessible to the server process, exposed to anyone with workspace trace-read access. Details Two defects combine. A field supplied through a tracing-propagation header was merged into the run without validation, allowing injection of run attributes including attachments (CWE-346). A type check intended to gate filesystem access did not match the type of the decoded input, so the guard never engaged (CWE-843). As a result, an attacker-named file is opened by the server and uploaded as a trace attachment by the background tracing thread (CWE-22). Who can exploit this Anyone reachable by HTTP can trigger the file read. Depending on how the distributed trace system is deployed, triggering may not require authentication. Retrieving the file contents requires read access to the destination LangSmith workspace. The upload uses the server's own configured API key and workspace, which the attacker cannot redirect, so a zero-access outsider cannot retrieve the result; a workspace member, or anyone who has compromised one, can. Remediation Upgrade the Python SDK to >= 0.8.18. Workarounds Until upgrading, do not expose TracingMiddleware to untrusted HTTP traffic, and limit workspace trace-read access to trusted members. Credits First reported by @Ryu7zz.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
GHSA-F4XH-W4CJ-QXQ8 has a CVSS score of 7.7 (High). The vector is network-reachable, low 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.8.18). Upgrading removes the vulnerable code path.
pip
langsmith (< 0.8.18)langsmith → 0.8.18 (pip)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 GHSA-F4XH-W4CJ-QXQ8 is reachable in your applications. Explore open-source security for your team.
See if GHSA-F4XH-W4CJ-QXQ8 is reachable in your applications. Get a demo
Already deployed Kodem? See GHSA-F4XH-W4CJ-QXQ8 in your environment →Upgrade langsmith to 0.8.18 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
GHSA-F4XH-W4CJ-QXQ8 is a high-severity path traversal vulnerability in langsmith (pip), affecting versions < 0.8.18. It is fixed in 0.8.18. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
GHSA-F4XH-W4CJ-QXQ8 has a CVSS score of 7.7 (High). 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.8.18 is affected.
Yes. GHSA-F4XH-W4CJ-QXQ8 is fixed in 0.8.18. Upgrade to this version or later.
Whether GHSA-F4XH-W4CJ-QXQ8 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.
Upgrade langsmith to 0.8.18 or later.