# GHSA-h829-5cg7-6hff: gitverify has improper tag signature verification

> An attacker can bypass tag signature verification in gitverify by using an unsigned annotated tag, undermining supply chain integrity checks.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Apr 2026
- **Also known as:** GO-2026-5416

## What is GHSA-h829-5cg7-6hff?

GHSA-h829-5cg7-6hff is a vulnerability in github.com/supply-chain-tools/gitverify, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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

## Which versions are affected by GHSA-h829-5cg7-6hff?

3 open source packages ship an affected version, including github.com/supply-chain-tools/gitverify.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/supply-chain-tools/gitverify` | Go | All versions | 0.0.0-20260421124901-c2c60da05d5c |
| `github.com/supply-chain-tools/gitverify` | Go | All versions | 0.0.0-20260421124901-c2c60da05d5c |
| `github.com/supply-chain-tools/gitverify` | Go | All versions | 0.0.0-20260421124901-c2c60da05d5c |

## How do I fix GHSA-h829-5cg7-6hff?

Upgrade github.com/supply-chain-tools/gitverify to 0.0.0-20260421124901-c2c60da05d5c or later.

## Is GHSA-h829-5cg7-6hff being exploited?

There is no known exploitation of GHSA-h829-5cg7-6hff in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-h829-5cg7-6hff and fix it if it is affected.

What it is: GHSA-h829-5cg7-6hff is a vulnerability in github.com/supply-chain-tools/gitverify, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-h829-5cg7-6hff in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/supply-chain-tools/gitverify (Go): affected all versions; fixed in 0.0.0-20260421124901-c2c60da05d5c
- github.com/supply-chain-tools/gitverify (Go): affected all versions; fixed in 0.0.0-20260421124901-c2c60da05d5c
- github.com/supply-chain-tools/gitverify (Go): affected all versions; fixed in 0.0.0-20260421124901-c2c60da05d5c

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-h829-5cg7-6hff/ (Markdown: https://insights.sbomify.com/GHSA-h829-5cg7-6hff/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-h829-5cg7-6hff

---
From sbomify Insights: https://insights.sbomify.com/GHSA-h829-5cg7-6hff/
Summaries are generated and may contain mistakes; the official description above is the record.