Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

LangSmith SDK: Streaming token events bypass output redaction

CVE-2026-41182GHSA-rr7j-v2q5-chgv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (langsmith 0.5.19; langsmith 0.7.31), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-41182: 0.21% estimated exploitation activity in the next 30 days; percentile 11.81 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The LangSmith SDK's output redaction controls (hideOutputs in JS, hideoutputs in Python) do not apply to streaming token events. When an LLM run produces streaming output, each chunk is recorded as a newtoken event containing the raw token value. These events bypass the redaction pipeline entirely — prepareRunCreateOrUpdateInputs (JS) and hiderunoutputs (Python) only process the inputs and outputs fields on a run, never the events array. As a result, applications relying on output redaction to prevent sensitive LLM output from being stored in LangSmith will still leak the full streamed content via run events. Details Both JS and Python SDKs are affected. The same pattern exists in both: - JS SDK: traceable.ts:997-1003 and traceable.ts:1044-1050 - Python SDK: runhelpers.py:1924 and runhelpers.py:1996 In both SDKs, newtoken events with raw kwargs.token values are added during streaming, and the redaction pipeline (hideOutputs in JS, hideoutputs in Python) only processes…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-rr7j-v2q5-chgv

  2. Revision 1 · created ·

    Published from osv record GHSA-rr7j-v2q5-chgv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41182

Advisory: LangSmith SDK: Streaming token events bypass output redaction
IDs: CVE-2026-41182, GHSA-rr7j-v2q5-chgv
Record: https://patchnext.com/advisories/cve-2026-41182 (revision 2, source checked 26 Oct 2026, 12:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: langsmith 0.5.19; langsmith 0.7.31. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm langsmith: affected <= 0.5.18; fixed in 0.5.19
- PyPI langsmith: affected <= 0.7.30; fixed in 0.7.31

## Suggested inspection (read-only)
- `npm ls langsmith --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.
- `python -m pip show langsmith`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on langsmith.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-rr7j-v2q5-chgv (OSV record GHSA-rr7j-v2q5-chgv lists affected ranges: npm langsmith >=0 =0 <0.7.31 (fixed))
- Verified: https://github.com/advisories/GHSA-rr7j-v2q5-chgv (GitHub-reviewed advisory GHSA-rr7j-v2q5-chgv lists affected ranges: npm langsmith >=0 =0 <=0.7.30)

Commands are suggestions: review each one before running it.

Loading voting…