CVE-2026-49834

sigstore-go: Multi-log threshold bypass via single compromised log

Published Jul 17, 2026 CVSS 3.1 · 5.9 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability is located in the sigstore-go library used for signing and verification. Before version 1.2.0, a verifier that is configured with WithTransparencyLog(N>1) or WithSignedCertificateTimestamps(N>1) counted witnesses per verified entry rather than per distinct log authority. That counting flaw allows a single compromised transparency log or CT log to satisfy a multi‑log threshold requirement, enabling an attacker to present a malicious signature that the verifier would incorrectly accept. The result is a loss of integrity in the verification process, which could permit tampered artifacts to be considered trustworthy. The flaw corresponds to CWE-347.

Affected Systems

Any software or container that incorporates sigstore-go and uses the WithTransparencyLog or WithSignedCertificateTimestamps options with a threshold greater than one is affected. All releases of sigstore-go older than v1.2.0 meet that condition. The issue is resolved in version 1.2.0 and later.

Risk and Exploitability

The CVSS score of 5.9 indicates moderate impact on integrity. The EPSS score, less than 1 %, reflects a very low likelihood of exploitation, and the vulnerability is not listed in CISA’s KEV catalog. An attacker would need to provide a malicious log entry that passes the single compromised log, thereby satisfying the multi‑log threshold. Successful exploitation would let an attacker forge signatures and bypass integrity checks in systems that rely on sigstore-go for artifact validation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the sigstore-go package to v1.2.0 or later across all affected deployments.
  • Temporarily set the multi‑log threshold to 1 (or disable the WithTransparencyLog/WithSignedCertificateTimestamps options) until the update can be applied, to avoid the vulnerability being exercised.
  • Perform a dependency audit of all projects and CI pipelines to confirm that all references to sigstore-go point to the patched version.

Generated by OpenCVE AI on July 30, 2026 at 23:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-9vcr-p3rj-q5q6 sigstore-go has a multi-log threshold bypass via single compromised log
History
Type Values Removed Values Added
First Time appeared Sigstore
Sigstore sigstore-go
Vendors & Products Sigstore
Sigstore sigstore-go
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title sigstore-go: Multi-log threshold bypass via single compromised log
Weaknesses CWE-347
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N'}

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 17, 2026, 7:42 PM
Reserved
Jun 1, 2026, 6:50 PM
Status
Analyzed
Published
Jul 17, 2026, 8:17 PM
Modified
Oct 24, 2026, 8:10 PM