GHSA-wcjx-v2wj-xg87 is a high-severity (CVSS 7.5) vulnerability in c2cciutils. A fix is available for c2cciutils — see the affected versions and patch details below.
C2C CI utils is vulnerable to DoS via pyasn dependency (CVE-2026-30922)
Real-World Exposure
c2cciutilsReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Pin vulnerable version of pyasn, see: See: https://github.com/advisories/GHSA-jr27-m4p2-rc6r
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | c2cciutils | all versions | 1.1.66pip install --upgrade 'c2cciutils==1.1.66' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for c2cciutils, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update c2cciutils to 1.1.66 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wcjx-v2wj-xg87 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-wcjx-v2wj-xg87 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-wcjx-v2wj-xg87. 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-wcjx-v2wj-xg87 in your dependencies?
O3 Security finds GHSA-wcjx-v2wj-xg87 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.