GHSA-87x9-7grx-m28v
HIGHGHSA-87x9-7grx-m28v is a high-severity (CVSS 7.5) CWE-770 vulnerability in github.com/notaryproject/notation-go. O3 Security confirms whether GHSA-87x9-7grx-m28v is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
notation-go has excessive memory allocation on verification
Blast Radius
github.com/notaryproject/notation-goReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
notation-go users will find their application using excessive memory when verifying signatures and the application will be finally killed, and thus availability is impacted.
Patches
The problem has been patched in the release v1.0.0-rc.3. Users should upgrade their notation-go packages to v1.0.0-rc.3 or above.
Workarounds
Users can review their own trust policy file and check if the identity string contains =#. Meanwhile, users should only put trusted certificates in their trust stores referenced by their own trust policy files, and make sure the authenticity validation is set to enforce
Credits
The notation-go project would like to thank Adam Korczynski (@AdamKorcz) for responsibly disclosing this issue during a security fuzzing audit sponsored by CNCF and Shiwei Zhang (@shizhMSFT) for root cause analysis and detailed vulnerability report.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/notaryproject/notation-go | all versions | 1.0.0-rc.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/notaryproject/notation-go. 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 github.com/notaryproject/notation-go to 1.0.0-rc.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-87x9-7grx-m28v 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-87x9-7grx-m28v 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-87x9-7grx-m28v. 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-87x9-7grx-m28v in your dependencies?
O3 detects GHSA-87x9-7grx-m28v across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.