Heap buffer overflow vulnerability in libjxl 0.12.0 via crafted PBM images to the jxl::extras::DecodeImagePNM function in file lib/extras/dec/pnm.cc.
CVE-2025-70103
Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. NVD baseline CVSS 7.3; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.3
- EG Score
- 7.3(medium)
- EG Risk
- 64(Attend)EG Risk 64/100SSVC: Attend
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%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
May 27, 2026
Last Modified
May 30, 2026
Advisory Details (5)
Auto-updated May 30, 2026lib/extras/dec/pnm.cc:554 heap-buffer-overflow in jxl::extras::DecodeImagePNM · Issue #4337 · libjxl/libjxl · GitHub
https://github.com/libjxl/libjxl/issues/4337oss-security - CVE-2025-70103: Heap-based Buffer Overflow in libjxl/cjxl via jxl::extras::DecodeImagePNM on crafted PBM file
http://www.openwall.com/lists/oss-security/2026/05/30/7sigdevel: "Security Advisory: CVE-2025-70103 - Heap-Based Bu…" - Infosec Exchange
https://infosec.exchange/@sigdevel/116642233929409910pocs/res/libjxl/2025/2 at main · sigdevel/pocs · GitHub
https://github.com/sigdevel/pocs/blob/main/res/libjxl/2025/2try to fix #4337
Upstream fix in progress (PR #4338 · libjxl/libjxl, state=closed)
https://github.com/libjxl/libjxl/pull/4338Vendor Advisories for CVE-2025-70103(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 / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libjxl0.11 (0.11.1-6ubuntu4.2) @ resolute | 2026-09-14 | ubuntu |
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
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| jpeg-xl | 0.10.3-1 ... 0.9.2-9 (57 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| jpeg-xl | 0.11.1-4, 0.11.1-5, 0.11.1-6, 0.11.2-0.1~deb13u1 | 0.11.2-0.1~deb13u2 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| jpeg-xl | 0.11.1-4 ... 0.11.2-5 (12 versions) | 0.11.2-5.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 10× in last 7d / 42× 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.
Showing the most recent 100 of 303 total refreshes for this CVE.
- 2026-09-16 05:14 UTCEPSS rescore
- 2026-09-15 03:10 UTCEPSS rescore
- 2026-09-14 07:39 UTCEG score recompute
- 2026-09-14 07:39 UTCVendor advisory
- 2026-09-14 07:39 UTCGHSA enrichment
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:00 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-08-30 01:21 UTCEPSS rescore
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-27 14:24 UTCEPSS rescore
- 2026-08-26 14:45 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 05:16 UTCEG score recompute
- 2026-08-25 05:16 UTCVendor advisory
- 2026-08-25 05:16 UTCGHSA enrichment
- 2026-08-24 14:16 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-08-23 15:00 UTCEG score recompute
- 2026-08-23 15:00 UTCVendor advisory
- 2026-08-23 15:00 UTCGHSA enrichment
- 2026-08-23 00:18 UTCEPSS rescore
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 20:34 UTCVendor advisory
- 2026-08-21 20:34 UTCGHSA enrichment
- 2026-08-21 01:29 UTCEG score recompute
- 2026-08-21 01:29 UTCVendor advisory
- 2026-08-21 01:29 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 11:18 UTCEG score recompute
- 2026-08-20 11:18 UTCVendor advisory
- 2026-08-20 11:18 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:46 UTCEPSS rescore
- 2026-08-17 09:15 UTCVendor advisory
- 2026-08-17 09:15 UTCGHSA enrichment
- 2026-08-16 15:26 UTCEG score recompute
- 2026-08-16 15:26 UTCVendor advisory
- 2026-08-16 15:26 UTCGHSA enrichment
- 2026-08-16 14:55 UTCEPSS rescore
- 2026-08-16 02:49 UTCEG score recompute
- 2026-08-16 02:49 UTCVendor advisory
- 2026-08-16 02:49 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 02:55 UTCEG score recompute
- 2026-08-15 02:55 UTCVendor advisory
- 2026-08-15 02:55 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 14:03 UTCVendor advisory
- 2026-08-14 14:03 UTCGHSA enrichment
- 2026-08-14 01:26 UTCEG score recompute
- 2026-08-14 01:26 UTCVendor advisory
- 2026-08-14 01:26 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 03:27 UTCVendor advisory
- 2026-08-13 03:27 UTCGHSA enrichment
- 2026-08-12 14:50 UTCEG score recompute
- 2026-08-12 14:50 UTCVendor advisory
- 2026-08-12 14:50 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 02:12 UTCEG score recompute
- 2026-08-12 02:12 UTCVendor advisory
- 2026-08-12 02:12 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 13:34 UTCVendor advisory
- 2026-08-11 13:34 UTCGHSA enrichment
- 2026-08-11 00:12 UTCEG score recompute
- 2026-08-11 00:12 UTCVendor advisory
- 2026-08-11 00:12 UTCGHSA enrichment
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-10 01:57 UTCEG score recompute
- 2026-08-10 01:57 UTCVendor advisory
- 2026-08-10 01:57 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 13:20 UTCVendor advisory
- 2026-08-09 13:20 UTCGHSA enrichment
- 2026-08-09 00:43 UTCEG score recompute
- 2026-08-09 00:43 UTCVendor advisory
- 2026-08-09 00:43 UTCGHSA enrichment
- 2026-08-08 16:36 UTCEPSS rescore
- 2026-08-08 12:06 UTCVendor advisory
- 2026-08-08 12:06 UTCGHSA enrichment
- 2026-08-07 23:29 UTCEG score recompute
- 2026-08-07 23:29 UTCVendor advisory
- 2026-08-07 23:29 UTCGHSA enrichment
- 2026-08-07 16:27 UTCEPSS rescore
- 2026-08-07 10:52 UTCVendor advisory
- 2026-08-07 10:52 UTCGHSA enrichment
- 2026-08-06 22:15 UTCEG score recompute
- 2026-08-06 22:15 UTCVendor advisory
- 2026-08-06 22:15 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownubuntu
- CVE-2004-0989EG 10.0EPSS p97HIGH
- CVE-2004-0990EG 10.0EPSS p98HIGH
- CVE-2004-1010EG 10.0EPSS p95HIGH
- CVE-2004-0941EG 10.0EPSS p96HIGH
- CVE-2004-0981EG 10.0EPSS p93HIGH
- CVE-2004-0882EG 10.0EPSS p96HIGH
- CVE-2004-0888EG 10.0EPSS p95HIGH
- CVE-2004-1012EG 10.0EPSS p93HIGH
- CVE-2004-1013EG 10.0EPSS p93HIGH
- CVE-2004-1018EG 10.0EPSS p97HIGH
Same CWE
10 shownCWE-122
- CVE-2016-9603NVD 5.5EG 9.9EPSS p91CRITICAL
- CVE-2017-20241EG 9.8CRITICAL
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2006-10002NVD 7.5EG 9.8CRITICAL
- CVE-2019-18296EG 9.8EPSS p92CRITICAL
- CVE-2019-18295EG 9.8EPSS p92CRITICAL
- CVE-2019-18293EG 9.8EPSS p92CRITICAL
- CVE-2019-18289EG 9.8EPSS p92CRITICAL
- CVE-2019-14901EG 9.8EPSS p97CRITICAL
- CVE-2019-14895EG 9.8EPSS p94CRITICAL
Frequently asked(5)
What is CVE-2025-70103?
When was CVE-2025-70103 disclosed?
Is CVE-2025-70103 actively exploited?
What is the CVSS score of CVE-2025-70103?
How do I remediate CVE-2025-70103?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-70103
Is Your Infrastructure Affected by CVE-2025-70103?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.