Which versions of github.com/supply-chain-tools/gitverify are affected by GHSA-H829-5CG7-6HFF?

github.com/supply-chain-tools/gitverify (go) versions < 0.0.0-20260421124901-c2c60da05d5c is affected.

Is there a fix for GHSA-H829-5CG7-6HFF?

Yes. GHSA-H829-5CG7-6HFF is fixed in 0.0.0-20260421124901-c2c60da05d5c. Upgrade to this version or later.

Is GHSA-H829-5CG7-6HFF exploitable, and should I be worried?

Whether GHSA-H829-5CG7-6HFF is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-H829-5CG7-6HFF is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-H829-5CG7-6HFF?

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

GHSA-H829-5CG7-6HFF

Q: What is GHSA-H829-5CG7-6HFF?

GHSA-H829-5CG7-6HFF is a medium-severity security vulnerability in github.com/supply-chain-tools/gitverify (go), affecting versions < 0.0.0-20260421124901-c2c60da05d5c. It is fixed in 0.0.0-20260421124901-c2c60da05d5c.

Q: Is there a fix for GHSA-H829-5CG7-6HFF?

Yes. GHSA-H829-5CG7-6HFF is fixed in 0.0.0-20260421124901-c2c60da05d5c. Upgrade to this version or later.

Q: Is GHSA-H829-5CG7-6HFF exploitable, and should I be worried?

Whether GHSA-H829-5CG7-6HFF is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-H829-5CG7-6HFF is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-H829-5CG7-6HFF?

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

GHSA-H829-5CG7-6HFF

GHSA-H829-5CG7-6HFF is a medium-severity security vulnerability in github.com/supply-chain-tools/gitverify (go), affecting versions < 0.0.0-20260421124901-c2c60da05d5c. It is fixed in 0.0.0-20260421124901-c2c60da05d5c.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

gitverify has improper tag signature verification

gitverify is still a prototype.

Workarounds

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.

Affected versions

github.com/supply-chain-tools/gitverify (< 0.0.0-20260421124901-c2c60da05d5c)

Security releases

github.com/supply-chain-tools/gitverify → 0.0.0-20260421124901-c2c60da05d5c (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Since the initial commit, fixed in c2c60da05d5c73621d0ce7ea02770bacd79ec8b1 (no semantic versions yet).

Frequently Asked Questions

What is GHSA-H829-5CG7-6HFF? GHSA-H829-5CG7-6HFF is a medium-severity security vulnerability in github.com/supply-chain-tools/gitverify (go), affecting versions < 0.0.0-20260421124901-c2c60da05d5c. It is fixed in 0.0.0-20260421124901-c2c60da05d5c.
Which versions of github.com/supply-chain-tools/gitverify are affected by GHSA-H829-5CG7-6HFF? github.com/supply-chain-tools/gitverify (go) versions < 0.0.0-20260421124901-c2c60da05d5c is affected.
Is there a fix for GHSA-H829-5CG7-6HFF? Yes. GHSA-H829-5CG7-6HFF is fixed in 0.0.0-20260421124901-c2c60da05d5c. Upgrade to this version or later.
Is GHSA-H829-5CG7-6HFF exploitable, and should I be worried? Whether GHSA-H829-5CG7-6HFF is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-H829-5CG7-6HFF is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-H829-5CG7-6HFF? Upgrade github.com/supply-chain-tools/gitverify to 0.0.0-20260421124901-c2c60da05d5c or later.