# GHSA-wcjx-v2wj-xg87: C2C CI utils is vulnerable to DoS via pyasn dependency (CVE-2026-30922)

> Attackers can cause denial of service in C2C CI utils via a vulnerable pyasn dependency, requiring library upgrades.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Mar 2026

## What is GHSA-wcjx-v2wj-xg87?

GHSA-wcjx-v2wj-xg87 is a denial of service vulnerability in c2cciutils, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pin vulnerable version of pyasn, see: See: https://github.com/advisories/GHSA-jr27-m4p2-rc6r

## Which versions are affected by GHSA-wcjx-v2wj-xg87?

2 open source packages ship an affected version, including c2cciutils.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `c2cciutils` | PyPI | All versions | 1.1.66 |
| `c2cciutils` | PyPI | All versions | 1.1.66 |

## How do I fix GHSA-wcjx-v2wj-xg87?

Upgrade c2cciutils to 1.1.66 or later.

## Is GHSA-wcjx-v2wj-xg87 being exploited?

There is no known exploitation of GHSA-wcjx-v2wj-xg87 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-wcjx-v2wj-xg87 and fix it if it is affected.

What it is: GHSA-wcjx-v2wj-xg87 is a denial of service vulnerability in c2cciutils, published on 26 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-wcjx-v2wj-xg87 in the wild and no public exploit code.

Affected packages and fixed versions:
- c2cciutils (PyPI): affected all versions; fixed in 1.1.66
- c2cciutils (PyPI): affected all versions; fixed in 1.1.66

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-wcjx-v2wj-xg87/ (Markdown: https://insights.sbomify.com/GHSA-wcjx-v2wj-xg87/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-wcjx-v2wj-xg87

---
From sbomify Insights: https://insights.sbomify.com/GHSA-wcjx-v2wj-xg87/
Summaries are generated and may contain mistakes; the official description above is the record.