Memory corruption via undersized PBM frame buffer
Published May 27, 2026 · Updated May 27, 2026
Heap buffer overflow in libjxl 0.12.0 allows remote attackers to corrupt memory by supplying a crafted PBM image for decoding. DecodeImagePNM allocates a 16-byte frame buffer after incorrect size calculations, then copies 24 bytes of pixel data without adequate bounds validation. The image must reach an application path that invokes DecodeImagePNM; the public proof of concept demonstrates an AddressSanitizer-detected crash.
Summary
What happened
Heap buffer overflow in libjxl 0.12.0 allows remote attackers to corrupt memory by supplying a crafted PBM image for decoding. DecodeImagePNM allocates a 16-byte frame buffer after incorrect size calculations, then copies 24 bytes of pixel data without adequate bounds validation. The image must reach an application path that invokes DecodeImagePNM; the public proof of concept demonstrates an AddressSanitizer-detected crash.
The record
- CVE
- CVE-2025-70103
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-122, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 2026Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- sigdevel crafted PBM 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