CVE-2026-44310

MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 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.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.4Exploit: 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. From 0.4.0 to before 0.15.0, CertVerifier.Verify() in pkg/git/verifier.go unconditionally dereferences certs[0] after sd.GetCertificates() without checking the slice length. A CMS/PKCS7 signed message with an empty certificate set is a structurally valid DER payload; GetCertificates() returns an empty slice with no error, causing an immediate index-out-of-range panic. On the gitsign --verify code path (the GPG-compatible mode invoked by git verify-commit), the panic is silently recovered by internal/io/streams.go's Wrap() function, which returns nil instead of an error. main.go then exits with code 0, causing exit-code-only verification callers to interpret the failed verification as success. This vulnerability is fixed in 0.15.0.

CVSS v3
5.4
EG Score
5.4(medium)
EPSS
1.6%
KEV
Not listed

Published

May 15, 2026

Last Modified

May 18, 2026

Advisory Details (1)

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

gitsign --verify panics on empty-certificate PKCS7 and exits 0, bypassing exit-code callers · Advisory · sigstore/gitsign · GitHub

https://github.com/sigstore/gitsign/security/advisories/GHSA-7c37-gx6w-8vc5

Vendor Advisories for CVE-2026-44310(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.15.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 36× 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-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:16 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-01 15:07 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-29 21:29 UTCEG score recompute
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-27 21:53 UTCEG score recompute
  15. 2026-06-27 03:08 UTCEPSS rescore
  16. 2026-06-26 20:12 UTCEG score recompute
  17. 2026-06-25 18:47 UTCEG score recompute
  18. 2026-06-23 21:33 UTCEPSS rescore
  19. 2026-06-21 14:56 UTCEPSS rescore
  20. 2026-06-21 14:56 UTCEPSS rescore
  21. 2026-06-21 01:59 UTCEPSS rescore
  22. 2026-06-19 19:25 UTCEPSS rescore
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-18 17:52 UTCEPSS rescore
  25. 2026-06-17 22:46 UTCEG score recompute
Show 58 more
  1. 2026-06-17 17:53 UTCEPSS rescore
  2. 2026-06-16 22:43 UTCEG score recompute
  3. 2026-06-16 17:52 UTCEPSS rescore
  4. 2026-06-15 23:33 UTCEG score recompute
  5. 2026-06-15 17:49 UTCEPSS rescore
  6. 2026-06-14 22:30 UTCEG score recompute
  7. 2026-06-13 23:18 UTCEG score recompute
  8. 2026-06-13 23:00 UTCEPSS rescore
  9. 2026-06-12 23:12 UTCEPSS rescore
  10. 2026-06-12 23:12 UTCEPSS rescore
  11. 2026-06-12 19:44 UTCEG score recompute
  12. 2026-06-11 20:32 UTCEG score recompute
  13. 2026-06-11 14:00 UTCEPSS rescore
  14. 2026-06-10 22:18 UTCEPSS rescore
  15. 2026-06-10 21:22 UTCEG score recompute
  16. 2026-06-10 13:22 UTCEPSS rescore
  17. 2026-06-10 13:22 UTCEPSS rescore
  18. 2026-06-09 22:11 UTCEG score recompute
  19. 2026-06-08 23:01 UTCEG score recompute
  20. 2026-06-08 14:17 UTCEPSS rescore
  21. 2026-06-08 14:17 UTCEPSS rescore
  22. 2026-06-07 23:50 UTCEG score recompute
  23. 2026-06-07 15:25 UTCEPSS rescore
  24. 2026-06-07 15:25 UTCEPSS rescore
  25. 2026-06-07 00:39 UTCEG score recompute
  26. 2026-06-06 13:47 UTCEPSS rescore
  27. 2026-06-06 13:47 UTCEPSS rescore
  28. 2026-06-06 01:28 UTCEG score recompute
  29. 2026-06-05 22:47 UTCEPSS rescore
  30. 2026-06-05 06:10 UTCEPSS rescore
  31. 2026-06-05 06:10 UTCEPSS rescore
  32. 2026-06-05 02:16 UTCEG score recompute
  33. 2026-06-04 13:12 UTCEPSS rescore
  34. 2026-06-04 13:12 UTCEPSS rescore
  35. 2026-06-04 03:05 UTCEG score recompute
  36. 2026-06-03 03:54 UTCEG score recompute
  37. 2026-06-02 20:13 UTCEPSS rescore
  38. 2026-06-02 04:43 UTCEG score recompute
  39. 2026-06-01 13:52 UTCEPSS rescore
  40. 2026-06-01 13:52 UTCEPSS rescore
  41. 2026-06-01 05:32 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

Frequently asked(5)

What is CVE-2026-44310?
CVE-2026-44310 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. From 0.4.0 to before 0.15.0, CertVerifier.Verify() in pkg/git/verifier.go unconditionally dereferences certs[0] after sd.GetCertificates() without checking the slice length. A CMS/PKCS7 signed message…
When was CVE-2026-44310 disclosed?
CVE-2026-44310 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-44310 actively exploited?
CVE-2026-44310 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44310?
CVE-2026-44310 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-44310?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44310, 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-44310

Explore →

Is Your Infrastructure Affected by CVE-2026-44310?

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

Start Free Scan →Browse All CVEs