Vulnerability Database · Debian · Package report

gimp: vulnerability history, versions and safety

gimp is a package in the Debian ecosystem. Vulert records 148 vulnerabilities for it across 61 releases, from Nov -0001 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
148 vulnerabilities recorded U148
i
73 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
57 in the last 12 months

Most recent disclosure 28 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on gimp i

Updated on 23 Oct 2026

Careful: 73 of the 148 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 148 vulnerabilities on record across 2026 years, 57 in the last year.

What to do: Plan around the 73 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 148 over 2026 years · 57 in the last year i
  • Latest disclosure 28 Aug 2026 i
  • Highest CVSS 9.1 i
  • With no published fix 73 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 gimp, 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.2.4-3 U24 No Details →
3.2.4-2 U35 No Details →
3.2.4-1 U35 No Details →
3.2.2-1 U42 No Details →
3.2.0-1 U43 No Details →
3.2.0~RC3-1 U44 No Details →
3.2.0~RC2-3.3 U49 No Details →
3.2.0~RC2-3.2 U49 No Details →
3.2.0~RC2-3.1 U52 No Details →
3.2.0~RC2-3 U53 No Details →
3.2.0~RC2-2 U57 No Details →
3.2.0~RC2-1 U57 No Details →
3.0.6-1 U57 No Details →
3.0.4-6.2 U57 No Details →
3.0.4-6.1 U57 No Details →
3.0.4-6 U63 No Details →
3.0.4-5 U63 No Details →
3.0.4-4 U65 No Details →
3.0.4-3 U73 No Details →
3.0.4-2 U73 No Details →
3.0.4-1 U73 No Details →
3.0.2-3.1 U73 No Details →
3.0.2-3 U73 No Details →
3.0.2-2 U73 No Details →
3.0.2-1 U73 No Details →
3.0.0-2 U73 No Details →
3.0.0-1 U73 No Details →
3.0.0~RC3-1 U73 No Details →
3.0.0~RC2-1 U73 No Details →
3.0.0~RC1-4 U73 No Details →
3.0.0~RC1-3 U73 No Details →
3.0.0~RC1-1 U73 No Details →
2.99.18-1 U73 No Details →
2.99.16-2 U73 No Details →
2.99.16-1 U73 No Details →
2.99.14-2 U73 No Details →
2.99.14-1 U73 No Details →
2.99.12-2 U73 No Details →
2.99.12-1 U73 No Details →
2.99.10-1 U73 No Details →
2.10.38-2 U73 No Details →
2.10.38-1 U73 No Details →
2.10.36-3 U73 No Details →
2.10.36-2 U73 No Details →
2.10.36-1 U73 No Details →
2.10.34-1 U73 No Details →
2.10.32-1 U73 No Details →
2.10.30-1 U73 No Details →
2.10.28-1 U73 No Details →
2.10.26-1 U73 No Details →
2.10.24-2 U73 No Details →
2.10.24-1 U73 No Details →
2.10.22-4 U88 No Details →
2.10.22-4+deb11u8 U35 No Details →
2.10.22-4+deb11u7 U44 No Details →
2.10.22-4+deb11u6 U50 No Details →
2.10.22-4+deb11u5 U55 No Details →
2.10.22-4+deb11u4 U60 No Details →
2.10.22-4+deb11u3 U62 No Details →
2.10.22-4+deb11u2 U79 No Details →
2.10.22-4+deb11u1 U79 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 0 5
  • 2006 2
  • 2007 10
  • 2009 4
  • 2011 12
  • 2012 14
  • 2013 6
  • 2016 2
  • 2017 12
  • 2018 1
  • 2022 2
  • 2023 1
  • 2024 8
  • 2025 18
  • 2026 51

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

03 Vulnerabilities

Recorded vulnerabilities for gimp

The 5 most severe of 148 vulnerabilities recorded for this package

Search all 148 in the database →

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 gimp

Is gimp safe to use?

Vulert records 148 vulnerabilities for gimp in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 148 not yet rated. 73 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does gimp have?

148 vulnerabilities are recorded for gimp in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 148 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 gimp vulnerabilities disclosed?

57 vulnerabilities were recorded for gimp in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. 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 gimp 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 gimp for upcoming vulnerabilities?

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