Metadata injection via truncated container box size
Published Sep 2, 2026 · Updated Sep 2, 2026
Integer conversion error in libjxl before 0.12.0 allows remote attackers to inject metadata through a crafted JPEG XL file. On 32-bit platforms, ParseBoxHeader truncated a 64-bit extended box size to size_t without verifying round-trip equality, causing codestream bytes to be reinterpreted as phantom metadata-box headers. Exploitation requires a crafted file to be decoded and can inject Exif, XMP, IPTC, or JUMBF metadata and trigger out-of-bounds reads.
Summary
What happened
Integer conversion error in libjxl before 0.12.0 allows remote attackers to inject metadata through a crafted JPEG XL file. On 32-bit platforms, ParseBoxHeader truncated a 64-bit extended box size to size_t without verifying round-trip equality, causing codestream bytes to be reinterpreted as phantom metadata-box headers. Exploitation requires a crafted file to be decoded and can inject Exif, XMP, IPTC, or JUMBF metadata and trigger out-of-bounds reads.
The record
- CVE
- CVE-2026-82522
- Published
- Sep 2, 2026
- Updated
- Sep 2, 2026
- Vendor
- Go standard library
- Product
- libjxl
- Classifications
- CWE-681, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 2, 2026CVE publishedPublication date reported by the CVE source.
- Sep 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.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
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