CVE-2026-48791

LOWPre-NVD 2.02.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 2.0 from GitHub Security Advisory (severity: LOW) published 2026-06-30. A secondary CVSS source baseline 2.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-57702 (ENISA EUVD) · GHSA-qqw8-7c2r-jxch (GitHub Security Advisories)Source: ENISA EUVD

2.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 2.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

sigstore-java is a sigstore java client for interacting with sigstore infrastructure. Version 2.0.0 erroneously removed verification of the integrated (Rekor entry) time) against the Fulcio certificate. Version 2.1.0 re-added this verification with enhancements that adhere to the Sigstore verification spec. The old sigstore-conformance test for this check was built incorrectly. This vulnerability impacts only users verifying bundles with dev.sigstore:sigstore-java:2.0.0. Older versions are not affected; it is fixed in dev.sigstore:sigstore-java:2.1.0 A malicious actor may exploit this if they were able to access a users system and exfiltrate the temporary private key used during signing and then reuse an old fulcio certificate later without requiring direct access to the user's credentials. Users may protect themselves by re-verifying their artifacts using the newest sigstore-java or another current sigstore client. Transparency logs may also be audited for unauthorized signatures for a suspected reused identity.

CVSS v3
2.0
EG Score
2.0LOWmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity20% × 45%
Impact severity (EG Severity): CVSS 2.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (2.0): severity, escalated by confirmed exploitation. This CVE's 2.0 is its impact severity (EG Severity), not escalated.

EG Severity
2.0 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
<0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 30, 2026

Last Modified

October 23, 2026

References (5)

Vendor Advisories for CVE-2026-48791(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavendev.sigstore:sigstore-java @ 2.1.0 (fixes = 2.0.0)—ghsa

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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
dev.sigstore:sigstore-java2.0.0
  • 2.0.0 up to 2.1.0: fixed in 2.1.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 3× in last 7d / 17× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 07:46 UTCGHSA enrichmentGHSA-qqw8-7c2r-jxch · GitHub severity LOW · GitHub CVSS 2.0
  2. 2026-11-01 07:46 UTCEG score recompute
  3. 2026-10-31 16:32 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  4. 2026-10-25 16:33 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  5. 2026-10-25 14:23 UTCEG score recompute
  6. 2026-10-23 19:34 UTCEG score recompute
  7. 2026-10-18 03:34 UTCEG score recompute
  8. 2026-10-13 18:24 UTCOSV refresh
  9. 2026-10-13 16:34 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  10. 2026-10-12 16:00 UTCEG score recompute
  11. 2026-10-11 19:43 UTCEG score recompute
  12. 2026-10-11 16:58 UTCEG score recompute
  13. 2026-10-11 14:22 UTCEG score recompute
  14. 2026-10-10 20:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  15. 2026-10-08 17:12 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  16. 2026-10-07 23:48 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  18. 2026-10-03 14:25 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  20. 2026-09-26 15:59 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  21. 2026-09-26 00:27 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  22. 2026-09-23 17:53 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  23. 2026-09-18 06:48 UTCEG score recompute
  24. 2026-09-16 14:08 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  25. 2026-09-16 05:15 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
Show 13 more
  1. 2026-09-13 09:16 UTCEG score recompute
  2. 2026-09-11 14:53 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  3. 2026-09-06 14:35 UTCEG score recompute
  4. 2026-08-27 22:41 UTCEG score recompute
  5. 2026-08-22 12:40 UTCEG score recompute
  6. 2026-08-16 12:47 UTCEG score recompute
  7. 2026-08-13 22:00 UTCEPSS rescoreEPSS <0.1% · below the 1st percentile
  8. 2026-08-13 13:19 UTCEG score recompute
  9. 2026-08-13 00:22 UTCEG score recompute
  10. 2026-08-01 12:49 UTCEG score recompute
  11. 2026-07-26 13:51 UTCEG score recompute
  12. 2026-07-23 03:18 UTCEG score recompute
  13. 2026-06-30 18:30 UTCEG score recompute

Related CVEs(same product + same CWE)

Same product

2 shown

Maven:dev.sigstore:sigstore-java

Frequently asked(5)

What is CVE-2026-48791?
CVE-2026-48791 is a low-severity vulnerability; its CVE record was published on June 30, 2026. sigstore-java is a sigstore java client for interacting with sigstore infrastructure. Version 2.0.0 erroneously removed verification of the integrated (Rekor entry) time) against the Fulcio certificate. Version 2.1.0 re-added this verification with enhancements that adhere to the Sigstore…
When was the CVE record for CVE-2026-48791 published?
The CVE record for CVE-2026-48791 was published on June 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-48791 actively exploited?
CVE-2026-48791 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48791?
CVE-2026-48791 has a CVSS base score of 2.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48791?
A fix for CVE-2026-48791 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48791 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-48791

Explore →

Is Your Infrastructure Affected by CVE-2026-48791?

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

Book a Demo →Browse All CVEs