VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

gtkwave: vulnerability history, versions and safety

gtkwave is a package in the Debian ecosystem. Vulert records 165 vulnerabilities for it across 1 release, from Jan 2024 to Apr 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
165 vulnerabilities recorded U165
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all gtkwave vulnerabilities

Vulert verdict on gtkwave i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 03 Apr 2024. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 165 vulnerabilities on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 165 over 1 year · 0 in the last year i
  • Latest disclosure 03 Apr 2024 i
  • Highest CVSS 7.8 i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for gtkwave, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
3.3.104-2 U165 Yes Details →

Newest 1 of 1 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 165

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 165 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for gtkwave

The 5 most severe of 165 vulnerabilities recorded for this package

Search all 165 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Arbitrary Code Execution Vulnerability in GTKWave Package - CVE-2023-37282 7.8 high 3.3.104+really3.3.118-0+deb11u1 08 Jan 2024
Critical Out-of-Bounds Write Vulnerabilities in GTKWave - CVE-2023-37417 7.8 high 3.3.104+really3.3.118-0+deb11u1 08 Jan 2024
Critical Out-of-Bounds Write Vulnerability in GTKWave - CVE-2023-37419 7.8 high 3.3.104+really3.3.118-0+deb11u1 08 Jan 2024
Arbitrary Code Execution Vulnerability in GTKWave 3.3.115 7.8 high 3.3.104+really3.3.118-0+deb11u1 08 Jan 2024
Critical Out-of-Bounds Write Vulnerability in GTKWave 3.3.115 7.8 high 3.3.104+really3.3.118-0+deb11u1 08 Jan 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About gtkwave

Is gtkwave safe to use?

Vulert records 165 vulnerabilities for gtkwave in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 165 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does gtkwave have?

165 vulnerabilities are recorded for gtkwave in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 165 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new gtkwave vulnerabilities disclosed?

0 vulnerabilities were recorded for gtkwave in the last 12 months, and the oldest entry in this database dates to 08 Jan 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of gtkwave are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor gtkwave for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the gtkwave version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.