CVE-2026-49834

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (7th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.5Exploit: 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.0, a verifier configured with WithTransparencyLog(N>1) or WithSignedCertificateTimestamps(N>1) counts verified witnesses per entry or per validation path rather than per log authority, allowing a single compromised transparency log or CT log to satisfy multi-log threshold requirements and defeat the multi-log policy. This issue is fixed in version 1.2.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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.2%
EPSS %ILE
7th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

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

Exploitation none (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.

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

July 9, 2026

Last Modified

July 30, 2026

Advisory Details (4)

Auto-updated Jul 17, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

v1.2.0

Patch available: sigstore/sigstore-go v1.2.0

https://github.com/sigstore/sigstore-go/releases/tag/v1.2.0
GitHub commit Patch Available

commit dbb07e62623e (sigstore/sigstore-go)

Patch available: sigstore/sigstore-go v1.2.0 (contains commit dbb07e62623e)

https://github.com/sigstore/sigstore-go/commit/dbb07e62623edd5b175fb9dd5a41dcb85a159207
GitHub pull request Patch Available

Prevent multi-log threshold bypasses via single compromised log

Patch available: sigstore/sigstore-go v1.2.0 (PR #633 merged 2026-05-27)

https://github.com/sigstore/sigstore-go/pull/633
GitHub advisoryMentions a patch (unverified)

Multi-log threshold bypass via single compromised log · Advisory · sigstore/sigstore-go · GitHub

https://github.com/sigstore/sigstore-go/security/advisories/GHSA-9vcr-p3rj-q5q6

Vendor Advisories for CVE-2026-49834(4)

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

Patch Availability(3)

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

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.0: fixed in 1.2.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 36× 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.

Showing the most recent 100 of 152 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 52 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  3. 2026-10-12 15:59 UTCEG score recompute
  4. 2026-10-11 19:43 UTCEG score recompute
  5. 2026-10-11 16:57 UTCEG score recompute
  6. 2026-10-11 14:21 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-01 16:00 UTCEG score recompute
  18. 2026-10-01 16:00 UTCVendor advisory
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-09-28 09:56 UTCEG score recompute
  22. 2026-09-28 09:56 UTCVendor advisory
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.2% · 6th percentile
Show 75 more
  1. 2026-09-24 11:22 UTCEG score recompute
  2. 2026-09-24 11:22 UTCVendor advisory
  3. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-09-23 05:51 UTCEG score recompute
  5. 2026-09-23 05:51 UTCVendor advisory
  6. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-09-18 05:26 UTCEG score recompute
  9. 2026-09-18 05:26 UTCVendor advisory
  10. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-09-13 23:45 UTCEG score recompute
  13. 2026-09-13 23:45 UTCVendor advisory
  14. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-09-13 08:16 UTCVendor advisory
  16. 2026-09-12 15:37 UTCEG score recompute
  17. 2026-09-12 15:37 UTCVendor advisory
  18. 2026-09-12 03:18 UTCEG score recompute
  19. 2026-09-12 03:18 UTCVendor advisory
  20. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-09-08 03:20 UTCEG score recompute
  24. 2026-09-08 03:20 UTCVendor advisory
  25. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  26. 2026-09-06 13:58 UTCEG score recompute
  27. 2026-09-06 13:58 UTCVendor advisory
  28. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  29. 2026-09-05 21:59 UTCEG score recompute
  30. 2026-09-05 21:59 UTCVendor advisory
  31. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  32. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  33. 2026-08-30 19:00 UTCVendor advisory
  34. 2026-08-30 06:41 UTCEG score recompute
  35. 2026-08-30 06:41 UTCVendor advisory
  36. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  37. 2026-08-27 21:43 UTCEG score recompute
  38. 2026-08-27 21:43 UTCVendor advisory
  39. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  40. 2026-08-27 00:54 UTCEG score recompute
  41. 2026-08-27 00:54 UTCVendor advisory
  42. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  43. 2026-08-26 03:46 UTCEG score recompute
  44. 2026-08-26 03:46 UTCVendor advisory
  45. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  46. 2026-08-25 10:03 UTCVendor advisory
  47. 2026-08-24 20:19 UTCEG score recompute
  48. 2026-08-24 20:19 UTCVendor advisory
  49. 2026-08-24 06:36 UTCVendor advisory
  50. 2026-08-23 18:17 UTCVendor advisory
  51. 2026-08-23 05:56 UTCEG score recompute
  52. 2026-08-23 05:56 UTCVendor advisory
  53. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  54. 2026-08-22 17:31 UTCVendor advisory
  55. 2026-08-22 05:01 UTCVendor advisory
  56. 2026-08-21 16:42 UTCVendor advisory
  57. 2026-08-21 03:46 UTCEG score recompute
  58. 2026-08-21 03:46 UTCVendor advisory
  59. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  60. 2026-08-20 15:13 UTCVendor advisory
  61. 2026-08-20 01:38 UTCVendor advisory
  62. 2026-08-19 09:16 UTCVendor advisory
  63. 2026-08-18 20:40 UTCEG score recompute
  64. 2026-08-18 20:40 UTCVendor advisory
  65. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  66. 2026-08-18 02:54 UTCVendor advisory
  67. 2026-08-17 14:08 UTCEG score recompute
  68. 2026-08-17 14:08 UTCVendor advisory
  69. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  70. 2026-08-17 01:49 UTCEG score recompute
  71. 2026-08-17 01:49 UTCVendor advisory
  72. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  73. 2026-08-16 13:30 UTCEG score recompute
  74. 2026-08-16 13:30 UTCVendor advisory
  75. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 1st percentile

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-49834?
CVE-2026-49834 is a high-severity vulnerability; its CVE record was published on July 9, 2026. sigstore-go is a Go library for Sigstore signing and verification. Prior to 1.2.0, a verifier configured with WithTransparencyLog(N>1) or WithSignedCertificateTimestamps(N>1) counts verified witnesses per entry or per validation path rather than per log authority, allowing a single compromised…
When was the CVE record for CVE-2026-49834 published?
The CVE record for CVE-2026-49834 was published on July 9, 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 July 30, 2026; the record at its source may have been updated since.
Is CVE-2026-49834 actively exploited?
CVE-2026-49834 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-49834?
CVE-2026-49834 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-49834?
A fix for CVE-2026-49834 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-49834 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-49834

Explore →

Is Your Infrastructure Affected by CVE-2026-49834?

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

Book a Demo →Browse All CVEs