CVE-2026-82522

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-09-02. a secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

libjxl before 0.12 contains an integer underflow vulnerability in the container box parser that allows remote attackers to inject arbitrary metadata by exploiting 64-bit box size truncation to size_t on 32-bit platforms. Attackers can supply a crafted JPEG XL file causing the decoder to parse attacker-controlled codestream bytes as phantom box headers, enabling injection of arbitrary metadata (Exif, XMP, IPTC, JUMBF) and potential out-of-bounds reads.

CVSS v3
5.4
EG Score
5.4(high)
EG Risk
24(Track)
EG Risk 24/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 computed
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

September 2, 2026

Last Modified

September 2, 2026

Advisory Details (4)

Auto-updated Sep 2, 2026
Patch available. Sources: github_release, github_pr, github_commit.
generic

libjxl < 0.12.0 Container Box Parser Integer Underflow via 32-bit Size Truncation | Advisories | VulnCheck

https://www.vulncheck.com/advisories/libjxl-container-box-parser-integer-underflow-via-32-bit-size-truncation
github_commit

commit 22ad80af1454 (libjxl/libjxl)

Fix landed in libjxl/libjxl commit 22ad80af1454 — awaiting tagged release

https://github.com/libjxl/libjxl/commit/22ad80af1454f0444ea34115e49ed40517147d68
github_pr

Several hardening / correctness / security fixes

Fix merged in libjxl/libjxl PR #4885 on 2026-07-01 — awaiting tagged release

https://github.com/libjxl/libjxl/pull/4885
github_release Patch Available

v0.12.0

Patch available: libjxl/libjxl v0.12.0

https://github.com/libjxl/libjxl/releases/tag/v0.12.0

Vendor Advisories for CVE-2026-82522(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
jpeg-xl0.10.3-1 ... 0.9.2-9 (57 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
jpeg-xl0.11.1-4 ... 0.11.2-5.1 (13 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
jpeg-xl0.11.1-4 ... 0.11.2-5.1 (13 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 44× 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.

  1. 2026-09-19 05:01 UTCEG score recompute
  2. 2026-09-19 05:00 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 02:49 UTCEG score recompute
  5. 2026-09-18 02:49 UTCGHSA enrichment
  6. 2026-09-17 00:37 UTCEG score recompute
  7. 2026-09-17 00:37 UTCGHSA enrichment
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 22:25 UTCEG score recompute
  11. 2026-09-15 22:25 UTCGHSA enrichment
  12. 2026-09-15 03:12 UTCEPSS rescore
  13. 2026-09-15 03:12 UTCEPSS rescore
  14. 2026-09-14 20:13 UTCGHSA enrichment
  15. 2026-09-13 18:01 UTCEG score recompute
  16. 2026-09-13 18:01 UTCGHSA enrichment
  17. 2026-09-12 15:50 UTCEG score recompute
  18. 2026-09-12 15:50 UTCGHSA enrichment
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-11 13:38 UTCEG score recompute
  22. 2026-09-11 13:38 UTCGHSA enrichment
  23. 2026-09-10 11:26 UTCEG score recompute
  24. 2026-09-10 11:26 UTCGHSA enrichment
  25. 2026-09-09 09:07 UTCEG score recompute
Show 19 more
  1. 2026-09-09 09:07 UTCGHSA enrichment
  2. 2026-09-08 22:01 UTCEPSS rescore
  3. 2026-09-08 06:55 UTCEG score recompute
  4. 2026-09-08 06:54 UTCGHSA enrichment
  5. 2026-09-07 04:42 UTCEG score recompute
  6. 2026-09-07 04:42 UTCGHSA enrichment
  7. 2026-09-06 13:48 UTCEPSS rescore
  8. 2026-09-06 02:30 UTCEG score recompute
  9. 2026-09-06 02:30 UTCGHSA enrichment
  10. 2026-09-05 15:31 UTCEPSS rescore
  11. 2026-09-05 00:18 UTCEG score recompute
  12. 2026-09-05 00:18 UTCGHSA enrichment
  13. 2026-09-04 05:07 UTCEPSS rescore
  14. 2026-09-03 22:04 UTCGHSA enrichment
  15. 2026-09-02 19:31 UTCEG score recompute
  16. 2026-09-02 19:31 UTCGHSA enrichment
  17. 2026-09-02 18:30 UTCEG score recompute
  18. 2026-09-02 17:46 UTCEG score recompute
  19. 2026-09-02 17:46 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-82522?
CVE-2026-82522 is a medium vulnerability published on September 2, 2026. libjxl before 0.12 contains an integer underflow vulnerability in the container box parser that allows remote attackers to inject arbitrary metadata by exploiting 64-bit box size truncation to size_t on 32-bit platforms. Attackers can supply a crafted JPEG XL file causing the decoder to parse…
When was CVE-2026-82522 disclosed?
CVE-2026-82522 was first published in the National Vulnerability Database on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82522 actively exploited?
CVE-2026-82522 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.4% of all scored CVEs.
What is the CVSS score of CVE-2026-82522?
CVE-2026-82522 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-82522?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82522, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-82522?

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

Start Free Scan →Browse All CVEs