GHSA-h829-5cg7-6hff — gitverify
Fix: supply-chain-tools/gitverify@c2c60daGHSA-h829-5cg7-6hff is a security vulnerability in github.com/supply-chain-tools/gitverify. A fix is available for github.com/supply-chain-tools/gitverify — see the affected versions and patch details below.
gitverify has improper tag signature verification
Real-World Exposure
github.com/supply-chain-tools/gitverifyReal-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
gitverify is still a prototype.
Impact
The bug is related to requireSignedTags which is on by default: an unsigned annotated tag would pass the verification. The commit pointed to by the tag would still have to be signed by a maintainer or a contributor.
Patches
Since the initial commit, fixed in c2c60da05d5c73621d0ce7ea02770bacd79ec8b1 (no semantic versions yet).
Workarounds
No
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/supply-chain-tools/gitverify | all versions | 0.0.0-20260421124901-c2c60da05d5cgo get github.com/supply-chain-tools/gitverify@v0.0.0-20260421124901-c2c60da05d5c |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/supply-chain-tools/gitverify, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/supply-chain-tools/gitverify to 0.0.0-20260421124901-c2c60da05d5c or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h829-5cg7-6hff 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-h829-5cg7-6hff can be triaged on real exposure rather than presence alone.
Tailored to GHSA-h829-5cg7-6hff. 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-h829-5cg7-6hff in your dependencies?
O3 Security finds GHSA-h829-5cg7-6hff across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.