| Package | Affected versions | Patched versions |
|---|---|---|
| langsmith | < 0.7.31 | 0.7.31 |
| langsmith | < 0.5.19 | 0.5.19 |
The LangSmith SDK's output redaction controls (hideOutputs in JS, hide_outputs in Python) do not apply to streaming token events. When an LLM run produces streaming output, each chunk is recorded as a new_token event containing the raw token value. These events bypass the redaction pipeline entirely — prepareRunCreateOrUpdateInputs (JS) and _hide_run_outputs (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.
Both JS and Python SDKs are affected. The same pattern exists in both:
traceable.ts:997-1003 and traceable.ts:1044-1050run_helpers.py:1924 and run_helpers.py:1996In both SDKs, new_token events with raw kwargs.token values are added during streaming, and the redaction pipeline (hideOutputs in JS, hide_outputs in Python) only processes inputs/outputs — never events.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free