Skip to main content
VulnerabilityPublished Updated

CVE-2023-37416: GTKWave · Out-of-bounds Write

Affects GTKWaveSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jan 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Debiandebian/gtkwavepkg:deb/debian/gtkwaveOther threatsAffected
  • =3.3.115
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should implement targeted mitigations beyond generic advice: 1) Immediately restrict the use of GTKWave 3.3.115 to trusted .vcd files only, enforcing strict file validation policies and blocking untrusted or unsolicited .vcd files from being opened. 2) Employ application whitelisting and sandboxing techniques for GTKWave to limit the impact of potential exploitation. 3) Monitor and audit usage of GTKWave binaries and related file access logs to detect anomalous behavior indicative of exploitation attempts. 4) Engage with the GTKWave community or maintainers to track patch releases and apply updates promptly once available. 5) Educate developers and engineers about the risks of opening unverified .vcd files and enforce secure handling procedures for simulation data. 6) Consider network segmentation for development environments to contain potential breaches. 7) Utilize endpoint detection and response (EDR) solutions to identify suspicious activities related to GTKWave processes.

Description

Multiple out-of-bounds write vulnerabilities exist in the VCD parse_valuechange portdump functionality of GTKWave 3.3.115. A specially crafted .vcd file can lead to arbitrary code execution. A victim would need to open a malicious file to trigger these vulnerabilities.This vulnerability concerns the out-of-bounds write when triggered via the GUI's legacy VCD parsing code.

References

Community reviews

Loading reviews…