Vulnerability in github.com/sigstore/sigstore-go (CVE-2026-54787)
Summary
Vulnerability in github.com/sigstore/sigstore-go (CVE-2026-54787). Risk of unauthorized operations or information disclosure. Exploitable via ExpiringKey. Mitigation: upgrade to 1.2.1 or later.
Original description
The description as published by the source.
sigstore-go fails to check signature timestamps against a signing key's validity period in github.com/sigstore/sigstore-go
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54787 has been found in github.com/sigstore/sigstore-go.
Attackers can target a specific entry point like ExpiringKey over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: upgrade github.com/sigstore/sigstore-go to 1.2.1 or later.
If unsure, ask your IT team or search "github.com/sigstore/sigstore-go CVE-2026-54787" on the vendor's site.
CVE-2026-54787 (github.com/sigstore/sigstore-go) — CWE-324 / CVSS v3 3.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ExpiringKey
Patched: 1.2.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-324) exists in github.com/sigstore/sigstore-go. Attackers reach the vulnerable code path via ExpiringKey.
Check the vendor advisory for the affected versions of github.com/sigstore/sigstore-go. Attack surface: ExpiringKey.
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure.
Update to 1.2.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/sigstore/sigstore-go' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/sigstore/sigstore-go' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/sigstore/sigstore-goを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/sigstore/sigstore-go to 1.2.1ステージング環境で 1.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2026-54787 sigstore-go
- Ubuntu UBUNTU-CVE-2026-54787 sigstore-go
References
- advisory github.com
- patch github.com
- patch github.com
- web github.com
- web github.com