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.
CVE-2026-12681
HIGHPre-NVD 8.98.9—
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 8.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.9
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.9Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.9
- EG Score
- 8.9(medium)
- EPSS
- 8.9%
- KEV
- Not listed
Published
June 24, 2026
Last Modified
June 25, 2026
Advisory Details (3)
Auto-updated Jun 24, 2026Patch available. Sources: github_commit, github_release, github.
github Patch Available
parseEfiSignatureList() does not skip SignatureHeaderSize vendor bytes — hash injection into trusted measurement list · Advisory · google/go-attestation · GitHub
https://github.com/google/go-attestation/security/advisories/GHSA-9r4w-jg96-92mvgithub_release Patch Available
v0.6.1
Patch available: google/go-attestation v0.6.1
https://github.com/google/go-attestation/releases/tag/v0.6.1github_commit Patch Available
commit b6e905e7ae52 (google/go-attestation)
Patch available: google/go-attestation v0.6.1 (contains commit b6e905e7ae52)
https://github.com/google/go-attestation/commit/b6e905e7ae52937f02b5ca494dd1c6a3ac7a1003Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Frequently asked(5)
What is CVE-2026-12681?
CVE-2026-12681 is a high vulnerability published on June 24, 2026. 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…
When was CVE-2026-12681 disclosed?
CVE-2026-12681 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12681 actively exploited?
CVE-2026-12681 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-12681?
CVE-2026-12681 has a CVSS v3 base score of 8.9 (NVD).
How do I remediate CVE-2026-12681?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12681, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-12681
Is Your Infrastructure Affected by CVE-2026-12681?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.