CVE-2026-41182
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 12% of all known CVEs.
References
Related Vulnerabilities
Other CWE-200 (Information Exposure) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-24919 | High | 8.6 | 100% | KEV + Ransom | - |
| CVE-2020-14181 | Medium | 5.3 | 100% | - | Fix |
| CVE-2021-34429 | Medium | 5.3 | 99% | - | Fix |
| CVE-2021-41277 | Critical | 10.0 | 97% | KEV | - |
| CVE-2016-2183 | High | 7.5 | 96% | - | Fix |
| CVE-2009-0580 | Medium | 4.3 | 94% | - | - |
Common questions
How do I fix CVE-2026-41182?
No published fix for CVE-2026-41182 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-41182 being actively exploited?
Not that we know of. CVE-2026-41182 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.21% is the estimated probability that it will be exploited in the next 30 days. That is higher than 12% of all scored CVEs.
How severe is CVE-2026-41182?
CVE-2026-41182 has a CVSS v3 base score of 5.3, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-41182
Markdown
[](https://tridentstack.com/cve/CVE-2026-41182)HTML
<a href="https://tridentstack.com/cve/CVE-2026-41182"><img src="https://tridentstack.com/cve/badge/CVE-2026-41182.svg" alt="CVE-2026-41182"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-05-29.