CVE-2026-41182

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
11.8%
KEV
Not listed

Published

April 23, 2026

Last Modified

May 29, 2026

References (1)

Affected Packages

(2 across 2 ecosystems)
npm(1)
PackageVulnerable rangeFixed inDependents
langsmith—0.5.19—
PyPI(1)
PackageVulnerable rangeFixed inDependents
langsmith0.0.0rc0 ... 0.7.9 (466 versions)0.7.31—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:15 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-01 15:06 UTCEPSS rescore
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-27 03:08 UTCEPSS rescore
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-24 14:05 UTCEPSS rescore
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-22 14:25 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-21 14:56 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 01:59 UTCEPSS rescore
  25. 2026-06-19 19:25 UTCEPSS rescore
Show 60 more
  1. 2026-06-18 17:52 UTCEPSS rescore
  2. 2026-06-18 17:52 UTCEPSS rescore
  3. 2026-06-17 17:53 UTCEPSS rescore
  4. 2026-06-16 17:52 UTCEPSS rescore
  5. 2026-06-15 17:49 UTCEPSS rescore
  6. 2026-06-14 12:25 UTCEG score recompute
  7. 2026-06-13 23:00 UTCEPSS rescore
  8. 2026-06-12 23:12 UTCEPSS rescore
  9. 2026-06-12 23:12 UTCEPSS rescore
  10. 2026-06-11 14:28 UTCEG score recompute
  11. 2026-06-11 14:00 UTCEPSS rescore
  12. 2026-06-10 22:18 UTCEPSS rescore
  13. 2026-06-10 13:22 UTCEPSS rescore
  14. 2026-06-10 13:22 UTCEPSS rescore
  15. 2026-06-10 03:36 UTCEG score recompute
  16. 2026-06-09 03:31 UTCEG score recompute
  17. 2026-06-08 14:17 UTCEPSS rescore
  18. 2026-06-08 14:17 UTCEPSS rescore
  19. 2026-06-07 18:40 UTCEG score recompute
  20. 2026-06-07 15:25 UTCEPSS rescore
  21. 2026-06-07 15:25 UTCEPSS rescore
  22. 2026-06-06 18:29 UTCEG score recompute
  23. 2026-06-06 13:47 UTCEPSS rescore
  24. 2026-06-06 13:47 UTCEPSS rescore
  25. 2026-06-05 22:47 UTCEPSS rescore
  26. 2026-06-05 16:39 UTCEG score recompute
  27. 2026-06-05 06:10 UTCEPSS rescore
  28. 2026-06-05 06:10 UTCEPSS rescore
  29. 2026-06-04 14:44 UTCEG score recompute
  30. 2026-06-04 13:12 UTCEPSS rescore
  31. 2026-06-04 13:12 UTCEPSS rescore
  32. 2026-06-03 14:42 UTCEG score recompute
  33. 2026-06-02 20:13 UTCEPSS rescore
  34. 2026-06-02 14:33 UTCEG score recompute
  35. 2026-06-01 14:30 UTCEG score recompute
  36. 2026-06-01 13:52 UTCEPSS rescore
  37. 2026-06-01 13:52 UTCEPSS rescore
  38. 2026-06-01 13:51 UTCEPSS rescore
  39. 2026-05-31 22:30 UTCEPSS rescore
  40. 2026-05-31 22:30 UTCEPSS rescore
  41. 2026-05-31 00:16 UTCEPSS rescore
  42. 2026-05-31 00:16 UTCEPSS rescore
  43. 2026-05-31 00:16 UTCEPSS rescore
  44. 2026-05-29 13:44 UTCEPSS rescore
  45. 2026-05-29 13:44 UTCEPSS rescore
  46. 2026-05-28 13:44 UTCEPSS rescore
  47. 2026-05-28 13:44 UTCEPSS rescore
  48. 2026-05-28 13:44 UTCEPSS rescore
  49. 2026-05-27 13:40 UTCEPSS rescore
  50. 2026-05-27 13:40 UTCEPSS rescore
  51. 2026-05-27 13:40 UTCEPSS rescore
  52. 2026-05-26 13:44 UTCEPSS rescore
  53. 2026-05-26 07:18 UTCEPSS rescore
  54. 2026-05-26 07:18 UTCEPSS rescore
  55. 2026-05-23 00:08 UTCEG score recompute
  56. 2026-05-20 22:38 UTCEPSS rescore
  57. 2026-05-20 22:38 UTCEPSS rescore
  58. 2026-05-20 16:04 UTCEG score recompute
  59. 2026-05-20 11:22 UTCEPSS rescore
  60. 2026-05-20 11:22 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41182?
CVE-2026-41182 is a medium vulnerability published on April 23, 2026. 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…
When was CVE-2026-41182 disclosed?
CVE-2026-41182 was first published in the National Vulnerability Database on April 23, 2026, with the most recent update on May 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41182 actively exploited?
CVE-2026-41182 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41182?
CVE-2026-41182 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-41182?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41182, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41182

Explore →

Is Your Infrastructure Affected by CVE-2026-41182?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs