---
id: "CVE-2026-126050"
page: "https://infrastack.ai/live/CVE-2026-126050"
kind: "vulnerability"
aliases: ["CVE-2026-126050"]
title: "apitrace: crafted trace file overflows heap buffer when opened"
severity: "high"
cvss: 8.5
epss: null
exploited: false
status: "open"
category: "other"
products: [{"name": "apitrace", "fixed": [], "affected": ">= 2.0, <= 14.0", "ecosystem": "vendor"}]
ecosystems: []
tags: ["apitrace", "graphics-debugging", "linux", "other", "windows"]
not_affected_if: ["apitrace-outside-2.0-14.0", "no-untrusted-trace-files"]
published_at: "2026-11-10T17:17:32+00:00"
first_seen_at: "2026-11-10T17:22:41+00:00"
updated_at: "2026-11-10T17:26:06+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-126050", "first_seen_at": "2026-11-10T17:22:41+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-11-10T17:26:06+00:00"}]
exploit_sources: []
---

# apitrace: crafted trace file overflows heap buffer when opened

Link for people: https://infrastack.ai/live/CVE-2026-126050 (this .md is for agents)

apitrace 2.0 through 14.0 trusts the 4-byte chunk length in a Snappy .trace file when reading it into a fixed 1223370-byte heap buffer. A crafted trace file writes past the end of that buffer when dumped, inspected or replayed. The upstream fix is a commit on master; no release after 14.0 is known.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:apitrace affected >= 2.0, <= 14.0 fixed no fixed version listed

## How to check

- Run 'apitrace version' (or check your package) : 14.0 and earlier back to 2.0 are affected.
- If you build from source, check that lib/trace/trace_file_snappy.cpp contains the commit 3890c5a fix.
- Until patched, do not open .trace files from untrusted sources with apitrace dump, trace, replay or the GUI.

## Fix

No released fix yet: latest release 14.0 is affected. The fix is upstream commit 3890c5a448addfd75ccbe1bd09e3075de6fb3395 on apitrace master, which rejects a Snappy chunk length larger than the 1223370-byte compressed cache. Build from master at or after that commit, or wait for a release newer than 14.0.

## Timeline

- 2026-11-10T17:22:41+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-126050
- 2026-11-10T17:26:06+00:00 analyst — Maintainer commit 3890c5a (2026-11-10) adds a chunk-length check in lib/trace/trace_file_snappy.cpp; no release after 14.0 found (14.0 tagged 2026-03-10, 18cfd38). VulnCheck lists 2.0-14.0 affected. No exploitation or PoC seen.

## Documents

- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/apitrace-2.0-through-14.0-heap-buffer-overflow-via-snappyfile-flushreadcache
- [fix] Patch: github.com https://github.com/apitrace/apitrace/commit/3890c5a448addfd75ccbe1bd09e3075de6fb3395

## From the sources

apitrace 2.0 through 14.0 contains a heap-based buffer overflow in SnappyFile::flushReadCache() that allows attackers to write past m_compressedCache via an oversized compressed chunk length. Attackers can supply a crafted .trace file whose 4-byte chunk length exceeds the fixed buffer size, corrupting heap memory when users dump, inspect, or replay it.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_