CVE-2026-54787

LOWPre-NVD 3.13.1—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 3.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (2nd percentile of EPSS-scored CVEs). 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, secondary
Trending — 3 sources updated this week
3.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 3.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

sigstore-go is a Go library for Sigstore signing and verification. Prior to 1.2.1, sigstore-go does not check a bundle signing timestamp against the validity window of an ExpiringKey wrapping a self-managed long-lived signing key without a certificate, which can allow an attacker holding expired key material to sign accepted bundles. This issue is fixed in version 1.2.1.

CVSS v3
3.1
EG Score
3.1LOWmedium confidence
EG Risk
19
EG Risk 19/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity31% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 31, 2026

Last Modified

September 10, 2026

References (5)

Vendor Advisories for CVE-2026-54787(6)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatspire1-14-main-1.14.7-0.3.hum12026-07-29redhat
redhattrivy-main-0.72.0-0.1.3.hum12026-07-29redhat
redhatspire1-15-main-1.15.2-0.3.hum12026-07-23redhat
redhatcosign-main-3.1.2-0.2.hum12026-07-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
sigstore-go0.7.1-2 ... 1.3.0-1 (8 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
sigstore-go0.7.1-2, 0.7.3-1, 0.7.3-2, 1.0.0-1, 1.1.4-1
  • every version up to 1.2.1-1: fixed in 1.2.1-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/sigstore/sigstore-go—
  • every version up to 1.2.1: fixed in 1.2.1
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same product + same vendor + same CWE)

Same product

2 shown

Debian:13:sigstore-go · Go:github.com/sigstore/sigstore-go

Same vendor

2 shown

redhat:RHSA-2026:44162

Frequently asked(5)

What is CVE-2026-54787?
CVE-2026-54787 is a low vulnerability published on July 31, 2026. sigstore-go is a Go library for Sigstore signing and verification. Prior to 1.2.1, sigstore-go does not check a bundle signing timestamp against the validity window of an ExpiringKey wrapping a self-managed long-lived signing key without a certificate, which can allow an attacker holding expired…
When was CVE-2026-54787 disclosed?
CVE-2026-54787 was first published on July 31, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54787 actively exploited?
CVE-2026-54787 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54787?
CVE-2026-54787 has a CVSS base score of 3.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54787?
A fix for CVE-2026-54787 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54787 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-54787?

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

Book a Demo →Browse All CVEs