← Vulnerability feed

Vulnerability record · CVE-2026-49834 · published 17 July 2026

CVE-2026-49834: Sigstore-go improper verification of cryptographic signature vulnerability

Sigstore · Sigstore Go

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.

7.5 CVSS 3.1 High EPSS 0.18% · top 93.1% CWE-347 · Improper verification of cryptographic signature
7.5CVSS 3.1 base score
0.18%EPSS exploitation probability, 30 days
NoNot in CISA KEV
1Affected product versions listed by NVD
4References
30 Jul 2026Last modified by NVD

Description

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:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Affected products

1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.

References

Track CVE-2026-49834 inside VULONE

Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.

Start free Open in platform

Related vulnerabilities

Same products first, then exploited flaws of the same weakness class.

7.5CVE-2024-45395Sigstore-go vulnerabilitysigstore-go, a Go library for Sigstore signing and verification, is susceptible to a denial of service attack in versions prior to 0.6.1 when a verif…EPSS 0.47%10.0CVE-2026-5430Wso2 api control plane improper verification of cryptographic signature vulnerabilityThe JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or supported. This allows an attacker t…KEVEPSS 0.59%9.5CVE-2026-48558SimpleHelp OIDC authentication bypass via unverified token signatureSimpleHelp 5.5.15 and earlier and 6.0 pre-release versions accept OIDC identity tokens without verifying their cryptographic signature. When OIDC is …KEVEPSS 5.7%analysed9.8CVE-2025-59718Fortinet FortiOS/FortiProxy SAML signature check bypass in FortiCloud SSOFortiOS, FortiProxy and FortiSwitchManager fail to properly verify the cryptographic signature of SAML responses used for FortiCloud SSO login. An un…KEVEPSS 68%analysed4.6CVE-2025-47827IGEL OS Secure Boot bypass via improper signature verificationIGEL OS before version 11 fails to properly verify a cryptographic signature in the igel-flash-driver module, allowing Secure Boot to be bypassed. A …KEVEPSS 4.9%analysed10.0CVE-2020-2021PAN-OS SAML signature verification bypass allows authentication bypassPAN-OS fails to properly verify SAML signatures when SAML authentication is enabled and the 'Validate Identity Provider Certificate' option is unchec…KEVEPSS 4.4%analysed5.5CVE-2013-3900Windows WinVerifyTrust Authenticode signature verification RCECVE-2013-3900 is a remote code execution flaw in how the Windows WinVerifyTrust function verifies Authenticode signatures on portable executable file…KEVEPSS 45%analysed7.8CVE-2020-1464Windows file signature validation spoofing allows loading of improperly signed filesWindows incorrectly validates file signatures, so a crafted file can be treated as properly signed. This lets an attacker bypass the security feature…KEVEPSS 39%analysed

Source: NIST National Vulnerability Database (record CVE-2026-49834), CISA KEV, FIRST EPSS (scores of 2026-09-27). This page is refreshed as NVD updates the record.