dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-41182

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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, 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. Version 0.5.19 of the JavaScript SDK and version 0.7.31 of the Python SDK fix the issue.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The LangSmith Client SDKs (JavaScript and Python) have a flaw where output redaction controls (hideOutputs/hide_outputs) do not apply to streaming token events. When LLM runs produce streaming output, each chunk is recorded as a new_token event containing raw token values in the events array, bypassing the redaction pipeline that only processes the inputs and outputs fields.

MitigationUpgrade to LangSmith JavaScript SDK version 0.5.19 or later, and Python SDK version 0.7.31 or later. Audit existing run events for any sensitive data that may have been leaked prior to the upgrade.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify LangSmith SDK version in use
    Run 'npm list langsmith' for JavaScript or 'pip show langsmith' for Python to see the installed version number
    Affected if The installed version is below 0.5.19 (JavaScript) or below 0.7.31 (Python)
  2. Verify streaming is enabled in your LLM calls
    Search codebase for streaming-related parameters such as 'stream=True', 'stream: true', 'streaming=true', or method calls that yield streaming chunks
    Affected if Streaming is enabled and the SDK version is vulnerable
  3. Inspect run event data for new_token entries
    Query LangSmith API or export run data and examine the events array - look for objects with event type 'new_token' that contain raw token content in the 'token' or 'text' field
    Affected if The events array contains 'new_token' events with unredacted/raw token values when hideOutputs/hide_outputs is enabled
  4. Check if output redaction is configured
    Search configuration for 'hideOutputs' (JavaScript) or 'hide_outputs' (Python) settings in your LangSmith initialization or client setup
    Affected if Redaction is configured but streaming is also in use, creating a false sense of security
  5. Compare affected version ranges to your installation
    Document your exact SDK version and confirm it falls before 0.5.19 (JS) or 0.7.31 (Python)
    Affected if Version is below the fixed releases and streaming with output redaction is in use

You are affected if you use LangSmith SDK versions below 0.5.19 (JavaScript) or below 0.7.31 (Python) with streaming enabled and have hideOutputs/hide_outputs configured, as your streaming token events will contain unredacted data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to LangSmith JavaScript SDK version 0.5.19 or later, and Python SDK version 0.7.31 or later. Audit existing run events for any sensitive data that may have been leaked prior to the upgrade.

Recommended fix High confidence

JavaScript SDK: version 0.5.19 or later; Python SDK: version 0.7.31 or later

  1. For JavaScript/TypeScript projects: Run `npm install @langchain/langsmith@^0.5.19` or update the dependency in package.json to version 0.5.19 or higher
  2. For Python projects: Run `pip install langsmith>=0.7.31` or update the dependency in requirements.txt/pyproject.toml to version 0.7.31 or higher
  3. After upgrading, verify the version installed matches or exceeds the fixed release by running `npm list @langchain/langsmith` (JS) or `pip show langsmith` (Python)
  4. Test that streaming LLM responses are properly redacted when hideOutputs/hide_outputs is enabled

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41182 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data