How severe is GHSA-jgvr-6x5w-hx5w?

No CVSS score has been assigned to GHSA-jgvr-6x5w-hx5w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jgvr-6x5w-hx5w?

GHSA-jgvr-6x5w-hx5w affects the following packages: kcl-lib (crates.io), zoo-kcl (PyPI). Ecosystems affected: crates.io, PyPI.

How do I fix GHSA-jgvr-6x5w-hx5w?

Update kcl-lib to 0.3.129 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jgvr-6x5w-hx5w is resolved across your whole dependency graph.

How do I detect GHSA-jgvr-6x5w-hx5w in my crates.io, PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kcl-lib. 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-jgvr-6x5w-hx5w 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-jgvr-6x5w-hx5w?

O3 pinpoints whether GHSA-jgvr-6x5w-hx5w 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-jgvr-6x5w-hx5w actively exploited in the wild?

No public exploit code has been indexed for GHSA-jgvr-6x5w-hx5w 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-jgvr-6x5w-hx5w published, and has it been updated?

GHSA-jgvr-6x5w-hx5w was published on August 20, 2026 and was last updated on August 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io🐍 PyPI

Not in CISA KEV

GHSA-jgvr-6x5w-hx5w

GHSA-jgvr-6x5w-hx5w is a remote code execution vulnerability in kcl-lib. O3 Security confirms whether GHSA-jgvr-6x5w-hx5w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Zoo Design Studio: Recursive KCL parsing is vulnerable to denial-of-service

Published

Aug 20, 2026

Updated

Aug 20, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Aug 20, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🦀kcl-lib🐍zoo-kcl

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

Description

Impact

Feeding a KCL program that wraps an expression in deep, unnecessary parentheses triggers the parser’s recursive expression -> unnecessarily_bracketed -> expression path. With enough nesting, the call stack grows until it exceeds the process stack limit, causing a stack overflow.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`kcl-lib`	all versions	0.3.129
🐍PyPI	`zoo-kcl`	all versions	0.3.129

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for kcl-lib. 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 kcl-lib to 0.3.129 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jgvr-6x5w-hx5w 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-jgvr-6x5w-hx5w 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-jgvr-6x5w-hx5w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Feeding a KCL program that wraps an expression in deep, unnecessary parentheses triggers the parser’s recursive `expression` -> `unnecessarily_bracketed` -> `expression` path. With enough nesting, the call stack grows until it exceeds the process stack limit, causing a stack overflow.

O3 Security · Impact-Aware SCA

Is GHSA-jgvr-6x5w-hx5w in your dependencies?

O3 detects GHSA-jgvr-6x5w-hx5w across crates.io, 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