CVE-2026-49834: sigstore-go is a Go library for Sigstore signing and verification

Q: How do I fix CVE-2026-49834?

sigstore-go: upgrade to 1.2.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-49834 being exploited?

CVE-2026-49834 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-49834 affect?

CVE-2026-49834 affects sigstore-go. Severity is medium (CVSS 5.9). 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

Routine

MEDIUM 5.9REMOTEUPGRADE

CVE-2026-49834 is a medium-severity flaw (CVSS 5.9) affecting sigstore-go. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 93%)
CISA exploited list	No
Weakness	CWE-347
Published	2026-07-17
Last modified	2026-10-24

Publisher (CNA): GitHub, Inc. · Vendor: sigstore

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-07-17 20:17 UTCPublished CVE record published
2026-10-24 20:10 UTCUpdated Record last modified

sigstore sigstore-go UPGRADE

Affected: < 1.2.0

Fixed in: 1.2.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy sigstore-go || rpm -q sigstore-go || sigstore-go --version

2. UPGRADE to 1.2.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade sigstore-go

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade sigstore-go

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-49834?

sigstore-go: upgrade to 1.2.0. Exact commands for each OS are on this page.

Is CVE-2026-49834 being exploited?

CVE-2026-49834 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-49834 affect?

CVE-2026-49834 affects sigstore-go. Severity is medium (CVSS 5.9). 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

How urgent is CVE-2026-49834?

Priority 27/100. Remotely exploitable, no login, no user action

References

← Back to latest CVEs