GHSA-c6jq-h4jp-72pr is a high-severity (CVSS 7.5) NULL Pointer Dereference vulnerability in aubio. A fix is available for aubio — see the affected versions and patch details below.
Aubio is vulnerable to a NULL pointer dereference in new_aubio_notes function
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-c6jq-h4jp-72pr plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
aubioReal-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
aubio v0.4.0 to v0.4.8 has a new_aubio_onset NULL pointer dereference in new_aubio_notes function within src/notes/notes.c.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | aubio | ≥ 0.4.0&&< 0.4.9 | 0.4.9pip install --upgrade 'aubio==0.4.9' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aubio, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update aubio to 0.4.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c6jq-h4jp-72pr 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-c6jq-h4jp-72pr can be triaged on real exposure rather than presence alone.
Tailored to GHSA-c6jq-h4jp-72pr. 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-c6jq-h4jp-72pr in your dependencies?
O3 Security finds GHSA-c6jq-h4jp-72pr across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.