CVE-2026-49834

MEDIUMPre-NVD 5.95.9
EchelonGraph scoreLOW confidence

This medium-severity CVE scores 5.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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: cna:github_m
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: —CVSS: 5.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

sigstore-go has a multi-log threshold bypass via single compromised log

Impact

_What kind of vulnerability is it? Who is impacted?_

A verifier configured with WithTransparencyLog(N>1) or WithSignedCertificateTimestamps(N>1) expected defense-in-depth against the compromise of a single log instance. However, threshold counting counted verified witnesses per-entry or per-validation-path rather than per-log-authority.

As a result, a single compromised transparency log could forge multiple entries with different indices, and a single compromised CT log could verify multiple times (either across multiple certificate chains or via multiple embedded SCTs), fully satisfying the multi-log threshold requirements and defeating the multi-log policy.

Note that this does not affect Cosign, as Cosign sets a threshold of 1.

Patches

_Has the problem been patched? What versions should users upgrade to?_

Upgrade to v1.1.5.

Workarounds

_Is there a way for users to fix or remediate the vulnerability without upgrading?_

There is no workaround, beyond relying on trusted logs.

CVSS v3
5.9
EG Score
5.9(low)
EPSS
—
KEV
Not listed

Published

July 9, 2026

Last Modified

July 9, 2026

Vendor 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.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× 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-07-15 23:43 UTCEG score recompute
  2. 2026-07-14 23:44 UTCEG score recompute
  3. 2026-07-13 23:45 UTCEG score recompute
  4. 2026-07-12 23:46 UTCEG score recompute
  5. 2026-07-11 23:46 UTCEG score recompute
  6. 2026-07-10 23:46 UTCEG score recompute
  7. 2026-07-09 23:46 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-49834?
CVE-2026-49834 is a medium vulnerability published on July 9, 2026. sigstore-go has a multi-log threshold bypass via single compromised log Impact What kind of vulnerability is it? Who is impacted? A verifier configured with WithTransparencyLog(N>1) or WithSignedCertificateTimestamps(N>1) expected defense-in-depth against the compromise of a single log instance.…
When was CVE-2026-49834 disclosed?
CVE-2026-49834 was first published in the National Vulnerability Database on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-49834?
CVE-2026-49834 has a CVSS v4.0 base score of 5.9 (CNA self-assessment; NVD's own analysis pending). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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

Explore the affected products and dependency analysis for 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