GHSA-mc9m-6fm9-pghc
GHSA-mc9m-6fm9-pghc is a security vulnerability in kcl-lib. O3 Security confirms whether GHSA-mc9m-6fm9-pghc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Zoo Design Studio: Memory-corruption in memory handling of lib-kcl
Real-World Exposure
kcl-lib🐍zoo-kclReal-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
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<Environment>>.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | kcl-lib | all versions | 0.2.153 |
| 🐍PyPI | zoo-kcl | all versions | 0.3.153 |
Detection & mitigation playbook
Open-source dependencyDetect
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.2.153 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mc9m-6fm9-pghc 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-mc9m-6fm9-pghc 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-mc9m-6fm9-pghc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-mc9m-6fm9-pghc in your dependencies?
O3 detects GHSA-mc9m-6fm9-pghc 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.