Google go-attestation up to 0.6.0 TPM parseEfiSignatureList improper validation of specified index, position, or offset in input

Summaryinfo

A vulnerability was found in Google go-attestation up to 0.6.0. It has been rated as problematic. This impacts the function parseEfiSignatureList of the component TPM Handler. Performing a manipulation results in improper validation of specified index, position, or offset in input. This vulnerability is reported as CVE-2026-12681. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Google go-attestation up to 0.6.0. This affects the function parseEfiSignatureList of the component TPM Handler. The manipulation with an unknown input leads to a improper validation of specified index, position, or offset in input vulnerability. CWE is classifying the issue as CWE-1285. The product receives input that is expected to specify an index, position, or offset into an indexable resource such as a buffer or file, but it does not validate or incorrectly validates that the specified index/position/offset has the required properties. This is going to have an impact on integrity. The summary by CVE is:

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.

The weakness was disclosed by prasanna8585 as GHSA-9r4w-jg96-92mv. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-12681 since 06/19/2026. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 06/24/2026).

Upgrading to version 0.6.1 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch b6e905e7ae52937f02b5ca494dd1c6a3ac7a1003 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Programming Language Software

Vendor

• Google

Name

• go-attestation

Version

• 0.1
• 0.2
• 0.3
• 0.4
• 0.5
• 0.6.0

License

• free

Website

• Vendor: https://www.google.com/
• Product: https://github.com/google/go-attestation/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion