LiveActive security incident?Get immediate response
CVE Record

CVE-2007-3126: Gimp before 2.8.22 allows context-dependent attackers to cause a denial of service (crash) via an ICO file...

Gimp before 2.8.22 allows context-dependent attackers to cause a denial of service (crash) via an ICO file with an InfoHeader containing a Height of zero, a similar issue to CVE-2007-2237.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is an old Gimp denial-of-service issue. A specially malformed ICO image can crash affected Gimp versions before 2.8.22. The sourced impact is availability loss of the application, not system compromise or data theft.

Executive priority

Treat as low urgency unless legacy Gimp is used in business-critical image-processing workflows. The practical risk is user disruption or job failure, not a sourced compromise path.

Technical view

CVE-2007-3126 concerns ICO parsing in Gimp before 2.8.22. An ICO InfoHeader with a zero Height can trigger a crash, described as similar to CVE-2007-2237. The bundle provides no CVSS, CWE, or evidence of code execution.

Likely exposure

Exposure is most likely on endpoints or workflows still using Gimp versions older than 2.8.22 and opening ICO files from untrusted or externally supplied sources.

Exploitation context

The source bundle does not show active exploitation, and KEV is false. Exploitation appears context-dependent: an affected Gimp instance must process a malformed ICO file. The documented outcome is a crash.

Researcher notes

Evidence is sparse and old. The CVE text, GNOME Bugzilla, and GIMP 2.8.22 release reference support the affected-version boundary and crash condition, but no CVSS, CWE, or exploit-in-the-wild claim is provided.

Mitigation direction

  • Upgrade Gimp to 2.8.22 or later where feasible.
  • Avoid opening untrusted ICO files with older Gimp versions.
  • Check GIMP or GNOME guidance for supported package fixes.
  • Remove obsolete Gimp versions from managed endpoints.

Validation and detection

  • Inventory installed Gimp versions across endpoints and build images.
  • Identify workflows that receive or process external ICO files.
  • Confirm upgraded systems report Gimp 2.8.22 or later.
  • Review crash reports for Gimp failures tied to ICO handling.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2007-3126 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.