Skip to main content
cve.nowby Sazabi
← Vulnerabilities
GO-2026-6893

Event type spoofing via UntrustedType in github.com/google/go-eventlog

Exploited
No known exploitation
Fix
Fixed in 0.0.3-0.20261001001437-1991f15bc4b0
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 0.0.3-0.20261001001437-1991f15bc4b0.

Published
Last modified
10/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

The github.com/google/go-eventlog Go library's TCG package exposes an Event.UntrustedType method that returns the event type from the TCG event log without checking it against the event data's digest. An attacker who can modify the event type field in a log can trick callers that dispatch on UntrustedType after ParseAndReplay into handling events of the wrong type, for events whose digests are not verified against EventData.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

In github.com/google/go-eventlog/tcg, Event exposes UntrustedType, which returns the raw event type header from the TCG event log without verifying that the event data matches its digest. Callers that dispatch on Event.UntrustedType after ParseAndReplay can be tricked by a modified event type field for events whose digests are not verified against EventData.

cve.now Index

10Pcve.now Index 10 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach10/20Affects Go packages
  • Severity?/10Unknown. No CVSS score or vendor rating
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

How the score works · Leaderboard

What to do

  • Upgrade to a fixed version: 0.0.3-0.20261001001437-1991f15bc4b0.

Timeline

  1. Advisory published
  2. Record last updated
  3. First seen by cve.now

Affected versions

  • github.com/google/go-eventlogGo

    fixed in 0.0.3-0.20261001001437-1991f15bc4b0

Evidence 4

  1. Patch
  2. Patch
  3. Report
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about GO-2026-6893

Is GO-2026-6893 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by GO-2026-6893?

github.com/google/go-eventlog (Go): before 0.0.3-0.20261001001437-1991f15bc4b0.Source: cve.now feed data

How do I fix GO-2026-6893?

Upgrade to a fixed version: 0.0.3-0.20261001001437-1991f15bc4b0.Source: cve.now feed data

Sources

More vulnerabilities