OESA-2026-1374 (CVE-2026-2239)
Vulnerability from osv_openeuler – Published: 2026-02-13 11:10 – Updated: 2026-08-06 11:10 – Source websiteThe GIMP is an image composition and editing program, which can be used for creating logos and other graphics for Web pages. The GIMP offers many tools and filters, and provides a large image manipulation toolbox, including channel operations and layers, effects, subpixel imaging and antialiasing, and conversions, together with multilevel undo. The GIMP offers a scripting facility, but many of the included scripts rely on fonts that we cannot distribute.
Security Fix(es):
GIMP is vulnerable to a heap-based buffer overflow when processing crafted PSD files, which can lead to application crash or denial of service.(CVE-2026-2239)
A vulnerability was found in GIMP (Image Processing Software) (affected version not known). It has been declared as problematic.The CWE definition for the vulnerability is CWE-191. The product subtracts one value from another, such that the result is less than the minimum allowable integer value, which produces a value that is not equal to the correct result.As an impact it is known to affect availability.There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0361).(CVE-2026-2271)
A vulnerability was found in GIMP (Image Processing Software) (the affected version unknown). It has been rated as problematic.Using CWE to declare the problem leads to CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.Impacted is availability.The exploit is available at bugzilla.redhat.com. It is declared as proof-of-concept.There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0361).(CVE-2026-2272)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"gimp-3.0.2-8.oe2403sp2.aarch64.rpm",
"gimp-debuginfo-3.0.2-8.oe2403sp2.aarch64.rpm",
"gimp-debugsource-3.0.2-8.oe2403sp2.aarch64.rpm",
"gimp-devel-3.0.2-8.oe2403sp2.aarch64.rpm",
"gimp-extension-goat-excercises-3.0.2-8.oe2403sp2.aarch64.rpm",
"gimp-libs-3.0.2-8.oe2403sp2.aarch64.rpm",
"gimp-plugin-aa-3.0.2-8.oe2403sp2.aarch64.rpm",
"gimp-plugin-python3-3.0.2-8.oe2403sp2.aarch64.rpm",
"gimp-vala-3.0.2-8.oe2403sp2.aarch64.rpm"
],
"src": [
"gimp-3.0.2-8.oe2403sp2.src.rpm"
],
"x86_64": [
"gimp-3.0.2-8.oe2403sp2.x86_64.rpm",
"gimp-debuginfo-3.0.2-8.oe2403sp2.x86_64.rpm",
"gimp-debugsource-3.0.2-8.oe2403sp2.x86_64.rpm",
"gimp-devel-3.0.2-8.oe2403sp2.x86_64.rpm",
"gimp-extension-goat-excercises-3.0.2-8.oe2403sp2.x86_64.rpm",
"gimp-libs-3.0.2-8.oe2403sp2.x86_64.rpm",
"gimp-plugin-aa-3.0.2-8.oe2403sp2.x86_64.rpm",
"gimp-plugin-python3-3.0.2-8.oe2403sp2.x86_64.rpm",
"gimp-vala-3.0.2-8.oe2403sp2.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP2",
"name": "gimp",
"purl": "pkg:rpm/openEuler/gimp\u0026distro=openEuler-24.03-LTS-SP2"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.0.2-8.oe2403sp2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "The GIMP is an image composition and editing program, which can be used for creating logos and other graphics for Web pages. The GIMP offers many tools and filters, and provides a large image manipulation toolbox, including channel operations and layers, effects, subpixel imaging and antialiasing, and conversions, together with multilevel undo. The GIMP offers a scripting facility, but many of the included scripts rely on fonts that we cannot distribute.\r\n\r\nSecurity Fix(es):\n\nGIMP is vulnerable to a heap-based buffer overflow when processing crafted PSD files, which can lead to application crash or denial of service.(CVE-2026-2239)\n\nA vulnerability was found in GIMP (Image Processing Software) (affected version not known). It has been declared as problematic.The CWE definition for the vulnerability is CWE-191. The product subtracts one value from another, such that the result is less than the minimum allowable integer value, which produces a value that is not equal to the correct result.As an impact it is known to affect availability.There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0361).(CVE-2026-2271)\n\nA vulnerability was found in GIMP (Image Processing Software) (the affected version unknown). It has been rated as problematic.Using CWE to declare the problem leads to CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control.Impacted is availability.The exploit is available at bugzilla.redhat.com. It is declared as proof-of-concept.There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2026-0361).(CVE-2026-2272)",
"id": "OESA-2026-1374",
"modified": "2026-08-06T11:10:24Z",
"published": "2026-02-13T11:10:24Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1374"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-2239"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-2271"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-2272"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L",
"type": "CVSS_V3"
}
],
"summary": "gimp security update",
"upstream": [
"CVE-2026-2239",
"CVE-2026-2271",
"CVE-2026-2272"
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.