| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00+ |
Summary
A vulnerability was found in GIMP. It has been rated as problematic. Affected by this issue is some unknown functionality of the component XCF Handler. The manipulation leads to stack-based overflow. This vulnerability is listed as CVE-2026-133007. The attack must be carried out locally. There is no available exploit.
Details
A vulnerability was found in GIMP (version unknown) and classified as problematic. This issue affects an unknown function of the component XCF Handler. The manipulation with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to CWE-121. The product writes past the end of a buffer that was allocated on the stack. Impacted is confidentiality. The summary by CVE is:
A flaw was found in GIMP. Opening a crafted XCF with a truncated uncompressed tile can expose uninitialized main-process stack memory through the imported layer's pixel data, which may include process addresses that weaken ASLR.
The advisory is shared at access.redhat.com. The identification of this vulnerability is CVE-2026-133007 since 11/19/2026. The exploitation is known to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.1VulDB Meta Temp Score: 4.1
VulDB Base Score: 2.8
VulDB Temp Score: 2.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.5
CNA Vector (redhat): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
11/19/2026 Advisory disclosed11/19/2026 CVE reserved
11/19/2026 VulDB entry created
11/19/2026 VulDB entry last update
Sources
Advisory: access.redhat.comStatus: Not defined
CNA: redhat
CVE: CVE-2026-133007 (🔒)
GCVE (CVE): GCVE-0-2026-133007
GCVE (VulDB): GCVE-100-440573
Entry
Created: 11/19/2026 18:19Changes: 11/19/2026 18:19 (60)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.