Is langsmith 0.8 vulnerable?

PyPI · 18 releases from 0.8.0 to 0.8.18 · latest langsmith is 0.15.1 · checked 20 Nov 2026

No known advisories in the last release

langsmith 0.8.18, the last 0.8 release, has no known advisories. 1 advisory affects earlier 0.8.x releases, so update to 0.8.18.

Update within 0.8:pip install 'langsmith>=0.8.18'

Is your project on an affected langsmith?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 0.8.x, affecting earlier releases

  • HighCVE-2026-59152GHSA-f4xh-w4cj-qxq819 Jun 2026

    LangSmith SDK TracingMiddleware: Arbitrary server-side file read

    Affected
    <0.8.18
    Fixed in
    0.8.18

Every langsmith 0.8.x release

Affected: 0.8.0 to 0.8.17. 0.8.18 is not affected. Latest langsmith: 0.15.1.

VersionKnown advisories
langsmith 0.8.18None
langsmith 0.8.17CVE-2026-59152
langsmith 0.8.16CVE-2026-59152
langsmith 0.8.15CVE-2026-59152
langsmith 0.8.14CVE-2026-59152
langsmith 0.8.12CVE-2026-59152
langsmith 0.8.11CVE-2026-59152
langsmith 0.8.10CVE-2026-59152
langsmith 0.8.9CVE-2026-59152
langsmith 0.8.8CVE-2026-59152
langsmith 0.8.7CVE-2026-59152
langsmith 0.8.6CVE-2026-59152
langsmith 0.8.5CVE-2026-59152
langsmith 0.8.4CVE-2026-59152
langsmith 0.8.3CVE-2026-59152
langsmith 0.8.2CVE-2026-59152
langsmith 0.8.1CVE-2026-59152
langsmith 0.8.0CVE-2026-59152

Which of your client projects are still on langsmith 0.8?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact langsmith version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other langsmith versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.