What is GHSA-MC9M-6FM9-PGHC?

GHSA-MC9M-6FM9-PGHC is a medium-severity race condition vulnerability in zoo-kcl (pip), affecting versions < 0.3.153. It is fixed in 0.3.153, 0.2.153. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.

Which packages are affected by GHSA-MC9M-6FM9-PGHC?

zoo-kcl (pip) versions < 0.3.153; kcl-lib (rust) versions < 0.2.153.

Is there a fix for GHSA-MC9M-6FM9-PGHC?

Yes. GHSA-MC9M-6FM9-PGHC is fixed in 0.3.153, 0.2.153. Upgrade to this version or later.

Is GHSA-MC9M-6FM9-PGHC exploitable, and should I be worried?

Whether GHSA-MC9M-6FM9-PGHC 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-MC9M-6FM9-PGHC 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-MC9M-6FM9-PGHC?

Upgrade: zoo-kcl to 0.3.153 or later, kcl-lib to 0.2.153 or later.

GHSA-MC9M-6FM9-PGHC in zoo-kcl

Q: Which packages are affected by GHSA-MC9M-6FM9-PGHC?

zoo-kcl (pip) versions < 0.3.153; kcl-lib (rust) versions < 0.2.153.

Q: Is there a fix for GHSA-MC9M-6FM9-PGHC?

Yes. GHSA-MC9M-6FM9-PGHC is fixed in 0.3.153, 0.2.153. Upgrade to this version or later.

Q: Is GHSA-MC9M-6FM9-PGHC exploitable, and should I be worried?

Whether GHSA-MC9M-6FM9-PGHC 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-MC9M-6FM9-PGHC 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-MC9M-6FM9-PGHC?

Upgrade: zoo-kcl to 0.3.153 or later, kcl-lib to 0.2.153 or later.

Summary

Zoo Design Studio: Memory-corruption in memory handling of lib-kcl

A race condition in kcl-lib can result in a use-after-free when accessing environments concurrently. During Vec reallocation, the previous buffer containing Box pointers is freed and replaced. A concurrent get_env operation that has already loaded a pointer to the old buffer may subsequently index into freed memory and retrieve a stale or corrupted Pin<Box>.

Impact

Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing. Typical impact: TOCTOU exploits, data corruption, or privilege escalation.

Affected versions

zoo-kcl (< 0.3.153) kcl-lib (< 0.2.153)

Security releases

zoo-kcl → 0.3.153 (pip) kcl-lib → 0.2.153 (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.153 or later; kcl-lib to 0.2.153 or later

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

Frequently Asked Questions

What is GHSA-MC9M-6FM9-PGHC? GHSA-MC9M-6FM9-PGHC is a medium-severity race condition vulnerability in zoo-kcl (pip), affecting versions < 0.3.153. It is fixed in 0.3.153, 0.2.153. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.
Which packages are affected by GHSA-MC9M-6FM9-PGHC?
- zoo-kcl (pip) (versions < 0.3.153)
- kcl-lib (rust) (versions < 0.2.153)
Is there a fix for GHSA-MC9M-6FM9-PGHC? Yes. GHSA-MC9M-6FM9-PGHC is fixed in 0.3.153, 0.2.153. Upgrade to this version or later.
Is GHSA-MC9M-6FM9-PGHC exploitable, and should I be worried? Whether GHSA-MC9M-6FM9-PGHC 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-MC9M-6FM9-PGHC 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-MC9M-6FM9-PGHC?
- Upgrade zoo-kcl to 0.3.153 or later
- Upgrade kcl-lib to 0.2.153 or later