Safeguard
Vulnerability Analysis•

CVE-2023-34087: High Memory Flaw in GTKWave EVCD Parsing

CVE-2023-34087 is an array index flaw in GTKWave 3.3.115 that a crafted .evcd file can trigger. Open only trusted files and apply your distro update.

Safeguard Security Team
3 min read

CVE-2023-34087 is a high severity (CVSS 7.8) improper array index validation in GTKWave 3.3.115. Opening a specially crafted .evcd file can lead to arbitrary code execution. Open only trusted waveform files, and apply the update from your distribution or the GTKWave project.

What's affected

  • GTKWave 3.3.115, per the NVD record and the Talos report title.
  • The record references a Debian LTS announcement from April 2024, which suggests distribution updates exist. We could not retrieve it or the Talos report, so confirm fixed package versions with your distribution.
  • The victim must open a malicious file.

The weakness is CWE-119, improper restriction of operations within the bounds of a memory buffer.

How to check if you're exposed

Check the installed version:

gtkwave --version

On Debian or Ubuntu you can also read the package version:

dpkg -l gtkwave

Compare it with the fixed package listed in your distribution security tracker. Look on build servers and shared lab machines too, because hardware design teams often install GTKWave on many hosts.

Ask engineers where waveform files come from. Files received from outside the team are the risk.

What to do now

  1. Update GTKWave through your package manager and confirm the new version.
  2. Do not open .evcd files from untrusted sources until the update is installed.
  3. If you build GTKWave from source, rebuild from a release that contains the fix, and check the project notes.
  4. Run viewers on workstations with limited privileges and no access to production secrets.
  5. Add GTKWave to your software inventory so future advisories reach the right owner.

If you track software dependencies, the free in-browser dependency scan can show which of your components carry known CVEs, and the Gold directory lists the same records in one place.

Why it matters

The flaw sits in how GTKWave parses variable length data in EVCD files. An index value taken from the file is not checked against the size of the array it addresses. That is a classic memory safety bug: the file steers where the program reads or writes in memory.

The user interaction requirement lowers the practical risk, but engineers exchange waveform dumps all the time, so a file from a vendor or a public repository can look routine. The CVSS vector reflects a local attack with user interaction and high impact.

The record shows this CVE is not in the CISA Known Exploited Vulnerabilities catalog.

Try it yourself

Click through it at your own pace, or open it full screen.

Quick check

Is exploitation remote?

Not directly. A victim must open a crafted .evcd file, which can arrive by email, download, or a shared repository.

Which version fixes it?

The sources we could read do not name one. Check the Debian LTS announcement and your distribution tracker for the fixed package version.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.