Skip to content
Fencer Intel
medium —

GHSA-h829-5cg7-6hff json

gitverify has improper tag signature verification

published 6mo ago modified 4mo ago also GO-2026-5416

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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

Patch / fix

  • go github.com/supply-chain-tools/gitverify 0.0.0-20260421124901-c2c60da05d5c

Is GHSA-h829-5cg7-6hff in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
go github.com/supply-chain-tools/gitverify
<0.0.0-20260421124901-c2c60da05d5c
0.0.0-20260421124901-c2c60da05d5c

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.