jxl-oxide is a pure Rust implementation of a JPEG XL decoder. Prior to jxl-grid 0.6.2, decoding a crafted JPEG XL image on a 32-bit platform can overflow length calculations in AlignedGrid::with_alloc_tracker and related grid and subgrid arithmetic. A 65536 x 65536 frame can pass the frame-area limit while overflowing the usize element count, causing modular, VarDCT, or filter rendering paths to allocate a backing buffer smaller than the logical grid. A tiny bitstream-controlled cropped frame combined with a huge canvas or requested region can also reach the vulnerable composition path in crates/jxl-render/src/blend.rs through ordinary render_frame(). Later mutable subgrid and raw-pointer operations can then perform attacker-controlled out-of-bounds writes, causing memory corruption, denial of service, or arbitrary code execution. This issue is fixed in jxl-grid version 0.6.2.
CVE-2026-52834
This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 97% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.3
- EG Score
- 7.3(medium)
- EG Risk
- 33(Track)EG Risk 33/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity73% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 3%
- KEV
- Not listed
Published
July 2, 2026
Last Modified
August 19, 2026
Advisory Details (4)
Auto-updated Aug 19, 2026RUSTSEC-2026-0151: jxl-grid: Out-of-bounds writes due to integer overflow in jxl-grid on 32-bit platforms › RustSec Advisory Database
https://rustsec.org/advisories/RUSTSEC-2026-0151.htmljxl-oxide v0.12.6
Patch available: tirr-c/jxl-oxide 0.12.6
https://github.com/tirr-c/jxl-oxide/releases/tag/0.12.6commit 3986dadd3926 (tirr-c/jxl-oxide)
Patch available: tirr-c/jxl-oxide 0.12.6 (contains commit 3986dadd3926)
https://github.com/tirr-c/jxl-oxide/commit/3986dadd3926a95656a642e74a0702d52f5c92e2Out-of-bounds writes due to integer overflow in jxl-grid on 32-bit platforms · Advisory · tirr-c/jxl-oxide · GitHub
https://github.com/tirr-c/jxl-oxide/security/advisories/GHSA-5pmv-rx8r-wmv5Vendor Advisories for CVE-2026-52834(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
crates.io(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| jxl-grid | — | 0.6.2 | — |
Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 01:07 UTCEG score recompute
- 2026-08-24 12:38 UTCEG score recompute
- 2026-08-23 11:00 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 10:00 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 09:01 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 19:21 UTCEG score recompute
- 2026-08-19 18:23 UTCEG score recompute
- 2026-07-30 22:01 UTCEG score recompute
- 2026-07-26 13:02 UTCEG score recompute
- 2026-07-23 03:19 UTCEG score recompute
- 2026-07-02 21:06 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-190 · CWE-122 · CWE-131
- CVE-2010-3254EG 10.0HIGH
- CVE-2008-2663EG 10.0EPSS p91HIGH
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2006-10002NVD 7.5EG 9.8CRITICAL
- CVE-2009-0947EG 9.8CRITICAL
- CVE-2005-1141EG 9.8CRITICAL
- CVE-2005-0102EG 9.8CRITICAL
- CVE-2004-1363EG 9.8EPSS p95CRITICAL
- CVE-2004-0434EG 9.8EPSS p94CRITICAL
- CVE-2003-0899EG 9.8EPSS p97CRITICAL
Frequently asked(5)
What is CVE-2026-52834?
When was CVE-2026-52834 disclosed?
Is CVE-2026-52834 actively exploited?
What is the CVSS score of CVE-2026-52834?
How do I remediate CVE-2026-52834?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52834
Is Your Infrastructure Affected by CVE-2026-52834?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.