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%, top 99% 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, 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%CVSS: 3.1Exploit: None knownExposed: 0

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.1(medium)
EG Risk
18(Track)
EG Risk 18/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

July 31, 2026

Last Modified

September 10, 2026

References (5)

Vendor Advisories for CVE-2026-54787(5)

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 / EcosystemFixed in / 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 rangeFixed inDependents
sigstore-go0.7.1-2 ... 1.3.0-1 (8 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
sigstore-go0.7.1-2, 0.7.3-1, 0.7.3-2, 1.0.0-1, 1.1.4-11.2.1-1—
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/sigstore/sigstore-go—1.2.1—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 99.5% of all scored CVEs.
What is the CVSS score of CVE-2026-54787?
CVE-2026-54787 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2026-54787?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54787, 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-54787

Explore →

Is Your Infrastructure Affected by CVE-2026-54787?

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

Start Free Scan →Browse All CVEs