Arbitrary heap write via uninitialized JPEG pointer
Published Jul 17, 2025 · Updated Sep 26, 2025
Heap buffer write in OpenCV 4.10.0 through 4.11.0 allows local users to corrupt memory by decoding a crafted JPEG 2000 image. In Jpeg2KOpenJpegDecoderBase::readHeader, rawImage remains uninitialized when header parsing fails, but opj_jp2_read_header still dereferences it and writes color-space and ICC-profile fields. Exploitation requires attacker-controlled image data and favorable stack and heap reuse; the demonstrated outcome is a heap-use-after-free crash, while the resulting write primitive enables arbitrary memory overwrite and code execution.
Summary
What happened
Heap buffer write in OpenCV 4.10.0 through 4.11.0 allows local users to corrupt memory by decoding a crafted JPEG 2000 image. In Jpeg2KOpenJpegDecoderBase::readHeader, rawImage remains uninitialized when header parsing fails, but opj_jp2_read_header still dereferences it and writes color-space and ICC-profile fields. Exploitation requires attacker-controlled image data and favorable stack and heap reuse; the demonstrated outcome is a heap-use-after-free crash, while the resulting write primitive enables arbitrary memory overwrite and code execution.
The record
- CVE
- CVE-2025-53644
- Published
- Jul 17, 2025
- Updated
- Sep 26, 2025
- Vendor
- OpenCV
- Product
- OpenCV
- Classifications
- CWE-457, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 17, 2025CVE publishedPublication date reported by the CVE source.
- Sep 26, 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=>= 4.10.0, < 4.12.0
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.
Weakness, pattern, technique
Public exploit references
- GitHub Security Lab JPEG 2000 proof of conceptproof of concept · demonstrated
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