Vulnerability in github.com/google/go-attestation (CVE-2026-12681)
Summary
Vulnerability in github.com/google/go-attestation (CVE-2026-12681). Risk of unauthorized operations or information disclosure. Exploitable via SignatureHeaderSize. Mitigation: upgrade to 0.6.1 or later.
Original description
The description as published by the source.
Improper Validation of Specified Index, Position, or Offset in Input vulnerability in Google go-attestation. parseEfiSignatureList() does not advance the buffer past vendor bytes before reading entries. For hashSHA256SigGUID lists, this allows attacker-controlled vendor header bytes to be appended to the trusted SHA256 hash list. A crafted TPM event log could inject arbitrary SHA256 hashes into the verifier's trusted measurement database, enabling a remote attestation verifier to accept a compromised boot state. This issue affects go-attestation: through 0.6.0.
Source: NIST National Vulnerability Database 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-12681 has been found in github.com/google/go-attestation.
Attackers can target a specific entry point like SignatureHeaderSize over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/google/go-attestation to 0.6.1 or later.
If unsure, ask your IT team or search "github.com/google/go-attestation CVE-2026-12681" on the vendor's site.
CVE-2026-12681 (github.com/google/go-attestation) — CWE-20
Attack surface: SignatureHeaderSize / EFI_SIGNATURE_LIST / hashSHA256SigGUID / buf
Patched: 0.6.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-20) exists in github.com/google/go-attestation. Attackers reach the vulnerable code path via SignatureHeaderSize.
Check the vendor advisory for the affected versions of github.com/google/go-attestation. Attack surface: SignatureHeaderSize / EFI_SIGNATURE_LIST / hashSHA256SigGUID / buf.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.6.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/google/go-attestation' . 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/google/go-attestation' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/google/go-attestationを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/google/go-attestation to 0.6.1ステージング環境で 0.6.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-12681 golang-github-google-go-attestation Fixed in: 0.6.1-1
- Ubuntu UBUNTU-CVE-2026-12681 golang-github-google-go-attestation
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com