Heap buffer overflow in apitrace trace file reader
Key facts
- Attack vector
- Local
- Privileges required
- None
- User interaction
- Passive
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- No fix listed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-122 and the CVSS impact.
Summary
apitrace 2.0 through 14.0 contains a heap-based buffer overflow (CWE-122) in SnappyFile::flushReadCache(). A crafted .trace file with an oversized 4-byte compressed chunk length writes past a fixed heap buffer. An attacker who supplies such a file corrupts heap memory when a user dumps, inspects, or replays it.
Written with Claude Haiku 5.5 from the sources below · 2026-11-11
Description from the CNA
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
The sources list no fixed version for apitrace.
Written with Claude Haiku 5.5 from the sources below · 2026-11-11
Timeline
- 2026-11-10 Threatist record created from CVE-2026-126050
- 2026-11-10 Alias added: GHSA-j4j9-82qf-ghhc
- 2026-11-10 CISA SSVC decision points changed
- 2026-11-10 Priority changed: MEDIUM → LOW
References
Sources
- CVE-2026-126050 · CVE Program
- CVE-2026-126050 · NVD
- FIRST EPSS
- GHSA-j4j9-82qf-ghhc · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences