LangSmith SDK: Streaming token events bypass output redaction
CVE-2026-41182 · GHSA-rr7j-v2q5-chgv · published 2026-04-16 · updated 2026-04-24
- Severity
- Medium
- CVSS score
- 5.3
- Chance of exploitation (EPSS)
- 0.21%
- Fixed in
- 0.7.31
- Exploitation No known exploitation
- Automatable Yes
- Technical impact Partial
- CISA SSVC
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 hiderun_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.
Upgrade langsmith to 0.7.31 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| langsmith | PyPI | <= 0.7.30 | 0.7.31 |
- CriticalPhoenix: Format String Injection in applyChatTemplatearize-phoenix
- CriticalFlowise: Unauthenticated OAuth2 token refresh endpoint returns access tokens — enables token theft for any connected serviceflowise
- CriticalMLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationmlflow
- CriticalvLLM has RCE In Video Processingvllm
- HighConfig revision hashes could expose password verifiersopenclaw
- Highn8n: Shared Credential Header Leak via HTTP Request Pagination Expressionn8n, n8n, n8n
- HighLangSmith SDK TracingMiddleware: Arbitrary server-side file readlangsmith
- HighLangSmith SDK: Public prompt pull deserializes untrusted manifests without trust boundary warninglangsmith, langchain
- MediumLangSmith Client SDK Affected by Server-Side Request Forgery via Tracing Header Injectionlangsmith
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.