Is langsmith 0.4 vulnerable?

npm · 13 releases from 0.4.0 to 0.4.12 · latest langsmith is 0.13.1 · checked 20 Nov 2026

Yes: 3 known advisories

Yes. langsmith 0.4.12, the last 0.4 release, is affected by 3 known security advisories (1 high, 2 medium), including CVE-2026-45134, CVE-2026-41182, CVE-2026-40190. 1 more affects earlier 0.4.x releases. Upgrade to 0.6.0 or later to fix all of them.

Upgrade with:npm install langsmith@0.6.0

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

Advisories affecting langsmith 0.4.12

  • 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

Fixed within 0.4.x, affecting earlier releases

  • 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

Every langsmith 0.4.x release

Affected: 0.4.0 to 0.4.12. Latest langsmith: 0.13.1.

VersionKnown advisories
langsmith 0.4.12CVE-2026-45134, CVE-2026-41182, CVE-2026-40190
langsmith 0.4.11CVE-2026-45134, CVE-2026-41182, CVE-2026-40190
langsmith 0.4.10CVE-2026-45134, CVE-2026-41182, CVE-2026-40190
langsmith 0.4.9CVE-2026-45134, CVE-2026-41182, CVE-2026-40190
langsmith 0.4.8CVE-2026-45134, CVE-2026-41182, CVE-2026-40190
langsmith 0.4.7CVE-2026-45134, CVE-2026-41182, CVE-2026-40190
langsmith 0.4.6CVE-2026-45134, CVE-2026-41182, CVE-2026-40190
langsmith 0.4.5CVE-2026-45134, CVE-2026-41182, CVE-2026-40190, CVE-2026-25528
langsmith 0.4.4CVE-2026-45134, CVE-2026-41182, CVE-2026-40190, CVE-2026-25528
langsmith 0.4.3CVE-2026-45134, CVE-2026-41182, CVE-2026-40190, CVE-2026-25528
langsmith 0.4.2CVE-2026-45134, CVE-2026-41182, CVE-2026-40190, CVE-2026-25528
langsmith 0.4.1CVE-2026-45134, CVE-2026-41182, CVE-2026-40190, CVE-2026-25528
langsmith 0.4.0CVE-2026-45134, CVE-2026-41182, CVE-2026-40190, CVE-2026-25528

Which of your client projects are still on langsmith 0.4?

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 npm registry. Refreshed daily.