Code execution via unchecked LBM data length
Published Dec 23, 2025 · Updated Dec 23, 2025
Stack-based buffer overflow in GIMP 3.0.6 allows remote attackers to execute arbitrary code after a user opens a crafted LBM file. The LBM parser copies user-supplied data into a stack buffer without first validating that the data length fits the destination. Exploitation requires user interaction and runs attacker-controlled code in the context of the GIMP process.
Summary
What happened
Stack-based buffer overflow in GIMP 3.0.6 allows remote attackers to execute arbitrary code after a user opens a crafted LBM file. The LBM parser copies user-supplied data into a stack buffer without first validating that the data length fits the destination. Exploitation requires user interaction and runs attacker-controlled code in the context of the GIMP process.
The record
- CVE
- CVE-2025-14423
- Published
- Dec 23, 2025
- Updated
- Dec 23, 2025
- Vendor
- GIMP
- Product
- GIMP
- Classifications
- CWE-121, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 23, 2025CVE publishedPublication date reported by the CVE source.
- Dec 23, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.0.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo