Read the docs
TI-2026-66623 Aliases GHSA-h829-5cg7-6hff

gitverify has improper tag signature verification

Priority LOW 38CWE-347Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
Security bypass
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-347.

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

Why it matters now

Fix Fixed github.com/supply-chain-tools/gitverify (Go): 0.0.0-20260421124901-c2c60da05d5c

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—github.com/supply-chain-tools/gitverify (Go)before 0.0.0-20260421124901-c2c60da05d5c0.0.0-20260421124901-c2c60da05d5cPatch availableGHSA-h829-5cg7-6hff
  • github.com/supply-chain-tools/gitverify (Go) Vendor— Affected before 0.0.0-20260421124901-c2c60da05d5c Fixed in 0.0.0-20260421124901-c2c60da05d5c Patch available GHSA-h829-5cg7-6hff

Remediation

  • Fix · GHSA-h829-5cg7-6hff github.com/supply-chain-tools/gitverify (Go) Fixed in 0.0.0-20260421124901-c2c60da05d5c Advisory →

Timeline

  1. 2026-10-03 Threatist record created from GHSA-h829-5cg7-6hff

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences