CVE-2026-44309

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
2.1%
KEV
Not listed

Published

May 15, 2026

Last Modified

May 18, 2026

Advisory Details (1)

Auto-updated Jun 17, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

gitsign verify accepts signatures over go-git-normalized bytes, enabling trust confusion on malformed commits · Advisory · sigstore/gitsign · GitHub

https://github.com/sigstore/gitsign/security/advisories/GHSA-7rmh-48mx-2vwc

Vendor Advisories for CVE-2026-44309(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/sigstore/gitsign—0.16.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-09 19:10 UTCEPSS rescore
  2. 2026-07-08 15:16 UTCEPSS rescore
  3. 2026-07-07 13:46 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-01 15:07 UTCEPSS rescore
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-29 21:29 UTCEG score recompute
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-28 14:07 UTCEPSS rescore
  12. 2026-06-27 23:14 UTCEG score recompute
  13. 2026-06-27 03:08 UTCEPSS rescore
  14. 2026-06-26 21:00 UTCEG score recompute
  15. 2026-06-25 18:47 UTCEG score recompute
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-24 14:05 UTCEPSS rescore
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-22 14:25 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-21 14:56 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 01:59 UTCEPSS rescore
  25. 2026-06-19 19:25 UTCEPSS rescore
Show 58 more
  1. 2026-06-18 17:52 UTCEPSS rescore
  2. 2026-06-18 17:52 UTCEPSS rescore
  3. 2026-06-18 04:03 UTCEG score recompute
  4. 2026-06-17 17:53 UTCEPSS rescore
  5. 2026-06-17 01:46 UTCEG score recompute
  6. 2026-06-15 23:33 UTCEG score recompute
  7. 2026-06-15 17:49 UTCEPSS rescore
  8. 2026-06-14 08:45 UTCEG score recompute
  9. 2026-06-13 23:00 UTCEPSS rescore
  10. 2026-06-13 06:25 UTCEG score recompute
  11. 2026-06-12 23:12 UTCEPSS rescore
  12. 2026-06-12 23:12 UTCEPSS rescore
  13. 2026-06-12 03:45 UTCEG score recompute
  14. 2026-06-11 14:00 UTCEPSS rescore
  15. 2026-06-11 01:32 UTCEG score recompute
  16. 2026-06-10 22:18 UTCEPSS rescore
  17. 2026-06-10 13:22 UTCEPSS rescore
  18. 2026-06-10 13:22 UTCEPSS rescore
  19. 2026-06-09 23:20 UTCEG score recompute
  20. 2026-06-08 21:06 UTCEG score recompute
  21. 2026-06-08 14:17 UTCEPSS rescore
  22. 2026-06-08 14:17 UTCEPSS rescore
  23. 2026-06-07 18:51 UTCEG score recompute
  24. 2026-06-07 15:25 UTCEPSS rescore
  25. 2026-06-07 15:25 UTCEPSS rescore
  26. 2026-06-06 16:38 UTCEG score recompute
  27. 2026-06-06 13:47 UTCEPSS rescore
  28. 2026-06-06 13:47 UTCEPSS rescore
  29. 2026-06-05 22:47 UTCEPSS rescore
  30. 2026-06-05 14:25 UTCEG score recompute
  31. 2026-06-05 06:10 UTCEPSS rescore
  32. 2026-06-05 06:10 UTCEPSS rescore
  33. 2026-06-04 13:12 UTCEPSS rescore
  34. 2026-06-04 13:12 UTCEPSS rescore
  35. 2026-06-04 12:12 UTCEG score recompute
  36. 2026-06-03 09:59 UTCEG score recompute
  37. 2026-06-02 20:13 UTCEPSS rescore
  38. 2026-06-02 07:46 UTCEG score recompute
  39. 2026-06-01 13:52 UTCEPSS rescore
  40. 2026-06-01 13:52 UTCEPSS rescore
  41. 2026-06-01 05:33 UTCEG score recompute
  42. 2026-05-31 22:30 UTCEPSS rescore
  43. 2026-05-31 22:30 UTCEPSS rescore
  44. 2026-05-31 00:16 UTCEPSS rescore
  45. 2026-05-31 00:16 UTCEPSS rescore
  46. 2026-05-29 13:44 UTCEPSS rescore
  47. 2026-05-29 13:44 UTCEPSS rescore
  48. 2026-05-28 13:44 UTCEPSS rescore
  49. 2026-05-28 13:44 UTCEPSS rescore
  50. 2026-05-27 13:40 UTCEPSS rescore
  51. 2026-05-27 13:40 UTCEPSS rescore
  52. 2026-05-26 13:44 UTCEPSS rescore
  53. 2026-05-26 07:18 UTCEPSS rescore
  54. 2026-05-23 00:07 UTCEG score recompute
  55. 2026-05-21 22:43 UTCEPSS rescore
  56. 2026-05-20 22:38 UTCEPSS rescore
  57. 2026-05-20 12:02 UTCEG score recompute
  58. 2026-05-20 11:22 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-44309?
CVE-2026-44309 is a medium vulnerability published on May 15, 2026. 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…
When was CVE-2026-44309 disclosed?
CVE-2026-44309 was first published in the National Vulnerability Database on May 15, 2026, with the most recent update on May 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44309 actively exploited?
CVE-2026-44309 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44309?
CVE-2026-44309 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-44309?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44309, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44309

Explore →

Is Your Infrastructure Affected by CVE-2026-44309?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs