langsmith vulnerabilities

Client library to connect to the LangSmith Observability and Evaluation Platform.

Registry
npm
Latest
0.13.1
License
MIT

4 known advisories

The latest version, 0.13.1, is not affected by any of them. Projects on older versions may be.

Update to the latest version:npm install langsmith@0.13.1

Is your project on an affected langsmith?

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

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

Security advisories for langsmith

  • HighCVE-2026-45134GHSA-3644-q5cj-c5c713 May 2026

    LangSmith SDK: Public prompt pull deserializes untrusted manifests without trust boundary warning

    Affected
    <0.6.0
    Fixed in
    0.6.0
  • MediumCVE-2026-41182GHSA-rr7j-v2q5-chgv16 Apr 2026

    LangSmith SDK: Streaming token events bypass output redaction

    Affected
    <0.5.19
    Fixed in
    0.5.19
  • MediumCVE-2026-40190GHSA-fw9q-39r9-c25210 Apr 2026

    LangSmith Client SDKs has Prototype Pollution in langsmith-sdk via Incomplete `__proto__` Guard in Internal lodash `set()`

    Affected
    <0.5.18
    Fixed in
    0.5.18
  • MediumCVE-2026-25528GHSA-v34v-rq6j-cj6p9 Feb 2026

    LangSmith Client SDK Affected by Server-Side Request Forgery via Tracing Header Injection

    Affected
    >=0.3.41 <0.4.6
    Fixed in
    0.4.6

Is your langsmith version vulnerable?

Which of your client projects still run an old langsmith?

NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other npm packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.