CVE-2026-126050 json
apitrace 2.0 through 14.0 Heap Buffer Overflow via SnappyFile::flushReadCache()
published yesterday modified yesterday also EUVD-2026-121408
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2026-126050 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- yesterday
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.5 | CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N |
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 4.0 | 8.5 | CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- apitrace apitrace
Classification
- Weakness
-
- CWE-122 Heap-based Buffer Overflow
References
-
github.com
/apitrace/apitrace/commit/3890c5a448addfd75ccbe1bd09e3075de6fb3395
patch
-
github.com
/apitrace/apitrace/blob/18cfd388ac47a9e00978b34d6c20341f3e2cdb56/lib/trace/trace_file_snappy.cpp#L215-L235
technical-description
-
vulncheck.com
/advisories/apitrace-2.0-through-14.0-heap-buffer-overflow-via-snappyfile-flushreadcache
third-party-advisory
Sources
- CVE List CVE-2026-126050
- NVD CVE-2026-126050
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.