← Back
UBUNTU-CVE-2026-24137
Vulnerability in golang-github-sigstore-sigstore (UBUNTU-CVE-2026-24137)
Summary
vulnerability in golang-github-sigstore-sigstore (UBUNTU-CVE-2026-24137). Data can be tampered with by attackers.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **UBUNTU-CVE-2026-24137** has been found in golang-github-sigstore-sigstore.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "golang-github-sigstore-sigstore UBUNTU-CVE-2026-24137" on the vendor's site.
UBUNTU-CVE-2026-24137 (golang-github-sigstore-sigstore) —
Attack vector: remote (network-reachable) / no user interaction
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.
❓ What is the problem
**A vulnerability** (unclassified) exists in golang-github-sigstore-sigstore.
📍 Affected scope
golang-github-sigstore-sigstore — .
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'golang-github-sigstore-sigstore' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'golang-github-sigstore-sigstore' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `golang-github-sigstore-sigstore` を grep し、稼働しているサービス・バージョンを把握する。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Ubuntu:24.04:LTS
golang-github-sigstore-sigstore
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:25.10
golang-github-sigstore-sigstore
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
Ubuntu:26.04:LTS
golang-github-sigstore-sigstore
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- report https://ubuntu.com/security/CVE-2026-24137
- report https://www.cve.org/CVERecord?id=CVE-2026-24137
- report https://github.com/sigstore/sigstore/commit/8ec410a2993ea78083aecf0e473a85453039496e
- report https://github.com/sigstore/sigstore/releases/tag/v1.10.4
- report https://github.com/sigstore/sigstore/security/advisories/GHSA-fcv2-xgw5-pqxf