What is GHSA-JGVR-6X5W-HX5W?

GHSA-JGVR-6X5W-HX5W is a medium-severity allocation of resources without limits or throttling vulnerability in zoo-kcl (pip), affecting versions < 0.3.129. It is fixed in 0.3.129. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.

Which packages are affected by GHSA-JGVR-6X5W-HX5W?

zoo-kcl (pip) versions < 0.3.129; kcl-lib (rust) versions < 0.2.129.

Is there a fix for GHSA-JGVR-6X5W-HX5W?

Yes. GHSA-JGVR-6X5W-HX5W is fixed in 0.3.129. Upgrade to this version or later.

Is GHSA-JGVR-6X5W-HX5W exploitable, and should I be worried?

Whether GHSA-JGVR-6X5W-HX5W is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-JGVR-6X5W-HX5W is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-JGVR-6X5W-HX5W?

Upgrade: zoo-kcl to 0.3.129 or later, kcl-lib to 0.3.129 or later.

GHSA-JGVR-6X5W-HX5W in zoo-kcl

Q: Which packages are affected by GHSA-JGVR-6X5W-HX5W?

zoo-kcl (pip) versions < 0.3.129; kcl-lib (rust) versions < 0.2.129.

Q: Is there a fix for GHSA-JGVR-6X5W-HX5W?

Yes. GHSA-JGVR-6X5W-HX5W is fixed in 0.3.129. Upgrade to this version or later.

Q: Is GHSA-JGVR-6X5W-HX5W exploitable, and should I be worried?

Whether GHSA-JGVR-6X5W-HX5W is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-JGVR-6X5W-HX5W is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-JGVR-6X5W-HX5W?

Upgrade: zoo-kcl to 0.3.129 or later, kcl-lib to 0.3.129 or later.

Summary

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

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.

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

Affected versions

zoo-kcl (< 0.3.129) kcl-lib (< 0.2.129)

Security releases

zoo-kcl → 0.3.129 (pip) kcl-lib → 0.3.129 (rust)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

zoo-kcl to 0.3.129 or later; kcl-lib to 0.3.129 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-JGVR-6X5W-HX5W? GHSA-JGVR-6X5W-HX5W is a medium-severity allocation of resources without limits or throttling vulnerability in zoo-kcl (pip), affecting versions < 0.3.129. It is fixed in 0.3.129. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
Which packages are affected by GHSA-JGVR-6X5W-HX5W?
- zoo-kcl (pip) (versions < 0.3.129)
- kcl-lib (rust) (versions < 0.2.129)
Is there a fix for GHSA-JGVR-6X5W-HX5W? Yes. GHSA-JGVR-6X5W-HX5W is fixed in 0.3.129. Upgrade to this version or later.
Is GHSA-JGVR-6X5W-HX5W exploitable, and should I be worried? Whether GHSA-JGVR-6X5W-HX5W is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-JGVR-6X5W-HX5W is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-JGVR-6X5W-HX5W?
- Upgrade zoo-kcl to 0.3.129 or later
- Upgrade kcl-lib to 0.3.129 or later