5.3
MEDIUM CVSS 3.1
CVE-2026-44309
gitsign verify accepts signatures over go-git-normalized bytes, enabling trust confusion on malformed commits
Description

Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. Prior to 0.16.0, gitsign verify and gitsign verify-tag re-encode commit/tag objects through go-git's EncodeWithoutSignature before checking the signature, instead of verifying against the raw git object bytes. For malformed objects with duplicate tree headers, git-core and go-git parse different trees: git-core uses the first, go-git uses the second. A signature crafted over the go-git-normalized form (second tree) passes gitsign verify while git-core resolves the commit to a completely different tree. This breaks the invariant that a verified signature, the commit semantics git-core presents to users, and the object hash logged in Rekor all refer to the same content. This vulnerability is fixed in 0.16.0.

INFO

Published Date :

May 15, 2026, 5:16 p.m.

Last Modified :

May 15, 2026, 6:16 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-44309 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Sigstore gitsign
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM [email protected]
Solution
Update Gitsign to version 0.16.0 or later to fix signature verification issues.
  • Update Gitsign to version 0.16.0.
  • Verify commits with correctly normalized objects.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-44309.

URL Resource
https://github.com/sigstore/gitsign/security/advisories/GHSA-7rmh-48mx-2vwc
https://github.com/sigstore/gitsign/security/advisories/GHSA-7rmh-48mx-2vwc
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-44309 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-44309 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-44309 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0

    May. 15, 2026

    Action Type Old Value New Value
    Added Reference https://github.com/sigstore/gitsign/security/advisories/GHSA-7rmh-48mx-2vwc
  • New CVE Received by [email protected]

    May. 15, 2026

    Action Type Old Value New Value
    Added Description Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. Prior to 0.16.0, gitsign verify and gitsign verify-tag re-encode commit/tag objects through go-git's EncodeWithoutSignature before checking the signature, instead of verifying against the raw git object bytes. For malformed objects with duplicate tree headers, git-core and go-git parse different trees: git-core uses the first, go-git uses the second. A signature crafted over the go-git-normalized form (second tree) passes gitsign verify while git-core resolves the commit to a completely different tree. This breaks the invariant that a verified signature, the commit semantics git-core presents to users, and the object hash logged in Rekor all refer to the same content. This vulnerability is fixed in 0.16.0.
    Added CVSS V3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
    Added CWE CWE-295
    Added CWE CWE-347
    Added Reference https://github.com/sigstore/gitsign/security/advisories/GHSA-7rmh-48mx-2vwc
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.