How severe is GHSA-qc22-xmq4-qg46?

No CVSS score has been assigned to GHSA-qc22-xmq4-qg46 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qc22-xmq4-qg46?

GHSA-qc22-xmq4-qg46 affects the following packages: c2cciutils (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-qc22-xmq4-qg46?

Update c2cciutils to 1.1.67 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qc22-xmq4-qg46 is resolved across your whole dependency graph.

How do I detect GHSA-qc22-xmq4-qg46 in my PyPI dependencies?

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.

How do I mitigate GHSA-qc22-xmq4-qg46 if there is no patch (or I can't update yet)?

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.

Is GHSA-qc22-xmq4-qg46 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qc22-xmq4-qg46 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-qc22-xmq4-qg46 published, and has it been updated?

GHSA-qc22-xmq4-qg46 was published on April 1, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

c2cciutils affected by CVE-2022-40896GHSA-qc22-xmq4-qg46

Fix: camptocamp/c2cciutils@9d54eab

GHSA-qc22-xmq4-qg46 is a security vulnerability in c2cciutils. A fix is available for c2cciutils — see the affected versions and patch details below.

Published

Apr 1, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍c2cciutils

Real-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

Pinned vulnerable version of Pygment CVE-2022-40896

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`c2cciutils`	all versions	1.1.67`pip install --upgrade 'c2cciutils==1.1.67'`

Detection & mitigation playbook

Open-source dependency

Detect
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.67 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qc22-xmq4-qg46 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.

Frequently Asked Questions

Pinned vulnerable version of Pygment [CVE-2022-40896](https://nvd.nist.gov/vuln/detail/CVE-2022-40896)

O3 Security · Impact-Aware SCA

Is GHSA-qc22-xmq4-qg46 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works