Is langsmith 0.5 vulnerable?
npm · 27 releases from 0.5.0 to 0.5.26 · latest langsmith is 0.13.1 · checked 20 Nov 2026
Yes: 1 known advisory
Yes. langsmith 0.5.26, the last 0.5 release, is affected by 1 known security advisory (1 high), including CVE-2026-45134. 2 more affect earlier 0.5.x releases. Upgrade to 0.6.0 or later to fix all of them.
npm install langsmith@0.6.0Is your project on an affected langsmith?
Look after several JavaScript apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting langsmith 0.5.26
LangSmith SDK: Public prompt pull deserializes untrusted manifests without trust boundary warning
- Affected
- <0.6.0
- Fixed in
- 0.6.0
Fixed within 0.5.x, affecting earlier releases
LangSmith SDK: Streaming token events bypass output redaction
- Affected
- <0.5.19
- Fixed in
- 0.5.19
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
Every langsmith 0.5.x release
Affected: 0.5.0 to 0.5.26. Latest langsmith: 0.13.1.
| Version | Known advisories |
|---|---|
| langsmith 0.5.26 | CVE-2026-45134 |
| langsmith 0.5.25 | CVE-2026-45134 |
| langsmith 0.5.24 | CVE-2026-45134 |
| langsmith 0.5.23 | CVE-2026-45134 |
| langsmith 0.5.22 | CVE-2026-45134 |
| langsmith 0.5.21 | CVE-2026-45134 |
| langsmith 0.5.20 | CVE-2026-45134 |
| langsmith 0.5.19 | CVE-2026-45134 |
| langsmith 0.5.18 | CVE-2026-45134, CVE-2026-41182 |
| langsmith 0.5.17 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.16 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.15 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.14 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.13 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.12 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.11 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.10 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.9 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.8 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.7 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.6 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.5 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.4 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.3 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.2 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.1 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
| langsmith 0.5.0 | CVE-2026-45134, CVE-2026-41182, CVE-2026-40190 |
Which of your client projects are still on langsmith 0.5?
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.