CVE-2024-51746

LOWNVD 1.81.8—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 1.8 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 82% 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
1.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 1.8Exploit: 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. gitsign may select the wrong Rekor entry to use during online verification when multiple entries are returned by the log. gitsign uses Rekor's search API to fetch entries that apply to a signature being verified. The parameters used for the search are the public key and the payload. The search API returns entries that match either condition rather than both. When gitsign's credential cache is used, there can be multiple entries that use the same ephemeral keypair / signing certificate. As gitsign assumes both conditions are matched by Rekor, there is no additional validation that the entry's hash matches the payload being verified, meaning that the wrong entry can be used to successfully pass verification. Impact is minimal as while gitsign does not match the payload against the entry, it does ensure that the certificate matches. This would need to be exploited during the certificate validity window (10 minutes) by the key holder.

CVSS v3
1.8
EG Score
1.8(medium)
EPSS
1.9%
KEV
Not listed

Published

November 5, 2024

Last Modified

April 15, 2026

References (1)

Affected Packages

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2024-51746?
CVE-2024-51746 is a low vulnerability published on November 5, 2024. Gitsign is a keyless Sigstore to signing tool for Git commits with your a GitHub / OIDC identity. gitsign may select the wrong Rekor entry to use during online verification when multiple entries are returned by the log. gitsign uses Rekor's search API to fetch entries that apply to a signature…
When was CVE-2024-51746 disclosed?
CVE-2024-51746 was first published in the National Vulnerability Database on November 5, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-51746 actively exploited?
CVE-2024-51746 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-51746?
CVE-2024-51746 has a CVSS v3 base score of 1.8 (NVD).
How do I remediate CVE-2024-51746?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-51746, 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-2024-51746

Explore →

Is Your Infrastructure Affected by CVE-2024-51746?

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

Start Free Scan →Browse All CVEs