CVE-2023-32650 is a high severity (CVSS 7.0) integer overflow in the FST parser of GTKWave 3.3.115 when built as a 32-bit binary. A crafted .fst file can cause memory corruption when a victim opens it. The vendor fixed it in version 3.3.118, and Debian 10 shipped a fixed package.
What's affected
The record lists GTKWave 3.3.115, compiled as a 32-bit binary, as affected. The Talos report TALOS-2023-1777 says the issue was fixed in version 3.3.118, available from SourceForge. The Talos timeline shows vendor contact in July 2023, a patch release on 31 December 2023 and public release on 8 January 2024.
Distribution packages carry their own versions. Debian's LTS announcement lists gtkwave 3.3.98+really3.3.118-0+deb10u1 as the fixed package for Debian 10 (buster), and it names this CVE. Check your own distribution's tracker for other releases.
The weakness is CWE-190, integer overflow or wraparound. It lives in the code that handles the geometry block of an FST file, specifically the maxhandle value. The 32-bit condition matters because the overflow depends on the size of the integer type.
How to check if you're exposed
Check the version and the architecture of the binary:
gtkwave --version
file $(which gtkwave)
On Debian and Ubuntu systems, list the installed package:
dpkg -l gtkwave
A 32-bit build of 3.3.115, or a distribution package older than the fixed one, is in scope. Also check container images and CI runners that install GTKWave for hardware verification work.
What to do now
- Find GTKWave installs on engineering workstations, CI runners and container images.
- Upgrade to 3.3.118 or later, or to your distribution's patched package.
- Prefer 64-bit builds where you can.
- Treat waveform files from outside your team as untrusted until you have upgraded.
- Add GTKWave to your software inventory so future advisories find it.
Why it matters
Integer overflows turn into memory problems when a computed size is too small for the data that follows. Here a size read from a file is combined with other values in 32-bit arithmetic, the result wraps around, and memory is used incorrectly. Talos reports memory corruption as the outcome.
A victim has to open a malicious file, so the risk is about shared waveform dumps, downloaded test cases and files from collaborators. The record does not report exploitation and the KEV flag is false.
Hardware design tools are rarely on a security team's radar, and they reach you as packages in images and lab machines. The free in-browser dependency scan helps you find such packages across manifests, and an inventory is the first step to knowing where they run.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Is the 64-bit build affected?
The record and Talos describe the issue for 32-bit builds of GTKWave 3.3.115.
Which version fixes CVE-2023-32650?
GTKWave 3.3.118, per Talos. Debian 10 ships 3.3.98+really3.3.118-0+deb10u1.
Sources
Last reviewed: 19 October 2026.