Application crash via misplaced bitmap validity check
Published Apr 5, 2025 · Updated Nov 3, 2025
Out-of-bounds read in Poppler before 25.04.0 allows attackers to crash PDF-processing applications with a crafted PDF file. JBIG2Bitmap::combine in JBIG2Stream.cc dereferences the destination bitmap without first checking whether its backing allocation succeeded; the check existed only at one caller. Exploitation requires an affected application to process the crafted file, and the confirmed consequence is an application crash.
Summary
What happened
Out-of-bounds read in Poppler before 25.04.0 allows attackers to crash PDF-processing applications with a crafted PDF file. JBIG2Bitmap::combine in JBIG2Stream.cc dereferences the destination bitmap without first checking whether its backing allocation succeeded; the check existed only at one caller. Exploitation requires an affected application to process the crafted file, and the confirmed consequence is an application crash.
The record
- CVE
- CVE-2025-32365
- Published
- Apr 5, 2025
- Updated
- Nov 3, 2025
- Vendor
- Libslirp Project
- Product
- Poppler
- Classifications
- CWE-125, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 5, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 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=0 <25.04.0
What conditions does exploitation require?
What is affected?
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