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.
CVE-2026-49834
MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 93% 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
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.9Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(medium)
- EG Risk
- 27(Track)EG Risk 27/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 computedSeverity59% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 6.6%
- KEV
- Not listed
Published
July 9, 2026
Last Modified
July 21, 2026
Advisory Details (4)
Auto-updated Jul 17, 2026Patch 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.0github_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/dbb07e62623edd5b175fb9dd5a41dcb85a159207github_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/633github 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-q5q6Vendor Advisories for CVE-2026-49834(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| 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 / 10× 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.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:18 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 03:42 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-09 23:46 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-347
Frequently asked(5)
What is CVE-2026-49834?
CVE-2026-49834 is a medium 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 21, 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 6.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49834?
CVE-2026-49834 has a CVSS v3 base score of 5.9 (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
Is Your Infrastructure Affected by CVE-2026-49834?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.