CVE-2026-49834

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 98% 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
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

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.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

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_pr 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 Patch Available

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 / 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

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.0—

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 121 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-49834?
CVE-2026-49834 is a high vulnerability 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 CVE-2026-49834 disclosed?
CVE-2026-49834 was first published in the National Vulnerability Database on July 9, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49834 actively exploited?
CVE-2026-49834 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 98.4% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49834, 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-49834

Explore →

Is Your Infrastructure Affected by CVE-2026-49834?

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

Start Free Scan →Browse All CVEs