CVE-2026-41182: LangSmith SDK: Streaming token events bypass output redaction

Published Apr 23, 2026
·
Updated

LangSmith Client SDKs provide SDK's for interacting with the LangSmith platform. Prior to version 0.5.19 of the JavaScript SDK and version 0.7.31 of the Python SDK, 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. Version 0.5.19 of the JavaScript SDK and version 0.7.31 of the Python SDK fix the issue.

Affected Software

5 affected components
LangSmith LangSmith JavaScript SDK<0.5.19
LangSmith LangSmith Python SDK<0.7.31
IBM Engineering AI Hub<=1.0.0
IBM Engineering AI Hub<=1.1.0
IBM Engineering AI Hub<=1.2.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade LangSmith JavaScript SDK to a version that resolves this vulnerability.

    Fixed in 0.5.19
  2. Upgrade

    Upgrade LangSmith Python SDK to a version that resolves this vulnerability.

    Fixed in 0.7.31

Event History

Apr 23, 2026
CVE Published
via MITRE·12:14 AM
Data Sourced
via MITRE·12:14 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:16 AM
DescriptionSeverityWeakness
Jul 14, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-41182?

CVE-2026-41182 has been classified as a high severity vulnerability due to its potential to bypass output redaction controls.

2

How do I fix CVE-2026-41182?

To fix CVE-2026-41182, upgrade to version 0.5.19 of the LangSmith JavaScript SDK or version 0.7.31 of the LangSmith Python SDK.

3

What are the main affected products in CVE-2026-41182?

CVE-2026-41182 affects the LangSmith JavaScript SDK versions earlier than 0.5.19 and the LangSmith Python SDK versions earlier than 0.7.31.

4

What is the impact of CVE-2026-41182 on data security?

CVE-2026-41182 can lead to unintended exposure of sensitive information due to improper output redaction in applications using the affected SDKs.

5

When was CVE-2026-41182 disclosed?

CVE-2026-41182 was disclosed as part of a security advisory by LangSmith and is currently available for remediation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203