Quick answers
- Is CVE-2026-82522 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82522 being exploited in the wild.
- How severe is CVE-2026-82522?
- Medium severity, with a CVSS score of 5.4, published 2 September 2026.
- Which products and versions are affected?
- libjxl libjxl before 0.12.
- Is there a fix for CVE-2026-82522?
- A patch was published on 2026-07-01: Fix committed in PR #4885 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82522 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-82522?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an integer underflow in libjxl's container box parser that occurs on 32-bit platforms due to truncation of 64-bit box size values to size_t. An attacker can supply a crafted JPEG XL file that exploits this type mismatch, causing the decoder to misparse codestream bytes as phantom box headers. This leads to injection of arbitrary metadata (Exif, XMP, IPTC, JUMBF) and potential out-of-bounds reads. The vulnerability requires no authentication or user interaction beyond opening a malicious file. A fix was committed in PR #4885 on 2026-07-01, which addresses the box_size type mismatch by properly handling size conversion on 32-bit platforms.
Affected products
- libjxl libjxl before 0.12
Timeline
- 2026-09-02: disclosed
- 2026-07-01: patched: Fix committed in PR #4885