How severe is GHSA-rr7j-v2q5-chgv?

GHSA-rr7j-v2q5-chgv has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-rr7j-v2q5-chgv?

GHSA-rr7j-v2q5-chgv affects the following packages: langsmith (npm), langsmith (PyPI). Ecosystems affected: npm, PyPI.

How do I fix GHSA-rr7j-v2q5-chgv?

Update langsmith to 0.5.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rr7j-v2q5-chgv is resolved across your whole dependency graph.

How do I detect GHSA-rr7j-v2q5-chgv in my npm, PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for langsmith. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-rr7j-v2q5-chgv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-rr7j-v2q5-chgv?

O3 pinpoints whether GHSA-rr7j-v2q5-chgv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rr7j-v2q5-chgv actively exploited in the wild?

No public exploit code has been indexed for GHSA-rr7j-v2q5-chgv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-rr7j-v2q5-chgv published, and has it been updated?

GHSA-rr7j-v2q5-chgv was published on April 16, 2026 and was last updated on July 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm🐍 PyPI

GHSA-rr7j-v2q5-chgv

MEDIUM

GHSA-rr7j-v2q5-chgv is a medium-severity (CVSS 5.3) vulnerability in langsmith. O3 Security confirms whether GHSA-rr7j-v2q5-chgv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

LangSmith SDK: Streaming token events bypass output redaction

Also known asCVE-2026-41182PYSEC-2026-2583

Published

Apr 16, 2026

Updated

Jul 13, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

📦langsmith🐍langsmith

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm, PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Summary

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.

Details

Both JS and Python SDKs are affected. The same pattern exists in both:

JS SDK: traceable.ts:997-1003 and traceable.ts:1044-1050
Python SDK: run_helpers.py:1924 and run_helpers.py:1996

In both SDKs, new_token events with raw kwargs.token values are added during streaming, and the redaction pipeline (hideOutputs in JS, hide_outputs in Python) only processes inputs/outputs — never events.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`langsmith`	all versions	0.5.19
🐍PyPI	`langsmith`	all versions	0.7.31

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for langsmith. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update langsmith to 0.5.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rr7j-v2q5-chgv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-rr7j-v2q5-chgv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-rr7j-v2q5-chgv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary 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

O3 Security · Impact-Aware SCA

Is GHSA-rr7j-v2q5-chgv in your dependencies?

O3 detects GHSA-rr7j-v2q5-chgv across npm, PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works