CVE-2026-52834

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-07-02. A secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-62513 (ENISA EUVD) · GHSA-5pmv-rx8r-wmv5 (GitHub Security Advisories)Source: ENISA EUVD

7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
33
EG Risk 33/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 2, 2026

Last Modified

October 27, 2026

Advisory Details (4)

Auto-updated Aug 19, 2026
Patch available. Sources: github, github_commit, github_release.
Web page

RUSTSEC-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.html
GitHub release Patch Available

jxl-oxide v0.12.6

Patch available: tirr-c/jxl-oxide 0.12.6

https://github.com/tirr-c/jxl-oxide/releases/tag/0.12.6
GitHub commit Patch Available

commit 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/3986dadd3926a95656a642e74a0702d52f5c92e2
GitHub advisoryMentions a patch (unverified)

Out-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-wmv5

Vendor 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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rustjxl-grid @ 0.6.2 (fixes <= 0.6.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
jxl-grid—
  • every version up to 0.6.2: fixed in 0.6.2
  • 0.0.0-0 up to 0.6.2: fixed in 0.6.2
—

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 42× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-11-01 07:45 UTCGHSA enrichmentGHSA-5pmv-rx8r-wmv5 · GitHub severity HIGH · GitHub CVSS 7.3
  3. 2026-11-01 07:45 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-27 13:26 UTCEG score recompute
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-25 14:21 UTCEG score recompute
  13. 2026-10-24 18:06 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-10-18 03:32 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-17 11:21 UTCEG score recompute
  24. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
Show 70 more
  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-10-13 14:54 UTCOSV refresh
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  5. 2026-10-12 15:58 UTCEG score recompute
  6. 2026-10-11 19:41 UTCEG score recompute
  7. 2026-10-11 16:56 UTCEG score recompute
  8. 2026-10-11 14:19 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  25. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  26. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  27. 2026-09-23 06:38 UTCEG score recompute
  28. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  29. 2026-09-18 20:35 UTCEG score recompute
  30. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  31. 2026-09-18 06:14 UTCEG score recompute
  32. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  33. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  34. 2026-09-14 00:15 UTCEG score recompute
  35. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  36. 2026-09-13 08:59 UTCEG score recompute
  37. 2026-09-12 14:15 UTCEG score recompute
  38. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  39. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  40. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  41. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-09-06 14:19 UTCEG score recompute
  43. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  44. 2026-09-05 23:51 UTCEG score recompute
  45. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  46. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  47. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  48. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  49. 2026-08-30 23:51 UTCEG score recompute
  50. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  51. 2026-08-30 11:22 UTCEG score recompute
  52. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  53. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  54. 2026-08-27 22:14 UTCEG score recompute
  55. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  56. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  57. 2026-08-25 01:07 UTCEG score recompute
  58. 2026-08-24 12:38 UTCEG score recompute
  59. 2026-08-23 11:00 UTCEG score recompute
  60. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  61. 2026-08-22 10:00 UTCEG score recompute
  62. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  63. 2026-08-21 09:01 UTCEG score recompute
  64. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  65. 2026-08-19 19:21 UTCEG score recompute
  66. 2026-08-19 18:23 UTCEG score recompute
  67. 2026-07-30 22:01 UTCEG score recompute
  68. 2026-07-26 13:02 UTCEG score recompute
  69. 2026-07-23 03:19 UTCEG score recompute
  70. 2026-07-02 21:06 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-52834?
CVE-2026-52834 is a high-severity vulnerability; its CVE record was published on July 2, 2026. 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…
When was the CVE record for CVE-2026-52834 published?
The CVE record for CVE-2026-52834 was published on July 2, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 27, 2026; the record at its source may have been updated since.
Is CVE-2026-52834 actively exploited?
CVE-2026-52834 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-52834?
CVE-2026-52834 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-52834?
A fix for CVE-2026-52834 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52834 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52834

Explore →

Is Your Infrastructure Affected by CVE-2026-52834?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs