CVE & CISA-KEV Catalog

CVE-2026-52834

HIGH
7.3
CVSS v3
NVD

Description

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.

How to fix

No published remediation has been found for this vulnerability's affected products yet.

Mitigation guidance may be in the linked vendor advisories in the References section below.

TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works

CVSS v3 Vector

Exploitability

Attack VectorLocal
Attack ComplexityHigh
Privileges RequiredNone
User InteractionNone
ScopeChanged

Impact

ConfidentialityLow
IntegrityLow
AvailabilityHigh

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H

Exploit Intelligence

0.13%probability of exploitation in 30 days
3rdpercentile

Low risk: more likely to be exploited than 3% of all known CVEs.

References

Related Vulnerabilities

Other CWE-122 (Heap-based Buffer Overflow) vulnerabilities, ordered by exploit likelihood. View all

CVESeverityCVSSEPSSExploitedFix
CVE-2015-3113Critical9.8100%KEVFix
CVE-2024-26256High7.888%-Fix
CVE-2020-25687Medium5.987%-Fix
CVE-2009-3459High8.887%KEVFix
CVE-2021-21017High8.886%KEV-
CVE-2020-25683Medium5.986%-Fix

Common questions

How do I fix CVE-2026-52834?

No published fix for CVE-2026-52834 has been found yet. Check the linked vendor advisories for guidance as it becomes available.

Is CVE-2026-52834 being actively exploited?

Not that we know of. CVE-2026-52834 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.13% is the estimated probability that it will be exploited in the next 30 days. That is higher than 3% of all scored CVEs.

How severe is CVE-2026-52834?

CVE-2026-52834 has a CVSS v3 base score of 7.3, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.

Embed a live status badge for CVE-2026-52834
CVE-2026-52834 severity badge

Markdown

[![CVE-2026-52834](https://tridentstack.com/cve/badge/CVE-2026-52834.svg)](https://tridentstack.com/cve/CVE-2026-52834)

HTML

<a href="https://tridentstack.com/cve/CVE-2026-52834"><img src="https://tridentstack.com/cve/badge/CVE-2026-52834.svg" alt="CVE-2026-52834"></a>

Find and fix vulnerabilities across your fleet

TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.

See how it worksStart freeThis CVE lookup is free and always will be.

This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-19.