CVE-2025-70103

HIGHNVD 7.37.3
EchelonGraph scoreMEDIUM confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. NVD baseline CVSS 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this weekElevated
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

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 computed
Severity73% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

May 27, 2026

Last Modified

May 30, 2026

Advisory Details (5)

Auto-updated May 30, 2026
No patch confirmed yet. Sources: github_pr.
generic

lib/extras/dec/pnm.cc:554 heap-buffer-overflow in jxl::extras::DecodeImagePNM · Issue #4337 · libjxl/libjxl · GitHub

https://github.com/libjxl/libjxl/issues/4337
generic

oss-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/7
generic

sigdevel: "Security Advisory: CVE-2025-70103 - Heap-Based Bu…" - Infosec Exchange

https://infosec.exchange/@sigdevel/116642233929409910
generic

pocs/res/libjxl/2025/2 at main · sigdevel/pocs · GitHub

https://github.com/sigdevel/pocs/blob/main/res/libjxl/2025/2
github_pr

try to fix #4337

Upstream fix in progress (PR #4338 · libjxl/libjxl, state=closed)

https://github.com/libjxl/libjxl/pull/4338

Vendor 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 / EcosystemFixed in / PatchReleasedSource
ubuntulibjxl0.11 (0.11.1-6ubuntu4.2) @ resolute2026-07-11ubuntu

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.

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 12× in last 7d / 52× 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 173 total refreshes for this CVE.

  1. 2026-07-27 14:13 UTCEPSS rescore
  2. 2026-07-27 10:11 UTCEG score recompute
  3. 2026-07-27 10:11 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-25 14:17 UTCEPSS rescore
  7. 2026-07-25 14:17 UTCEPSS rescore
  8. 2026-07-24 14:17 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:02 UTCEG score recompute
  12. 2026-07-22 14:08 UTCEPSS rescore
  13. 2026-07-21 15:24 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:30 UTCEPSS rescore
  16. 2026-07-19 14:30 UTCEPSS rescore
  17. 2026-07-19 02:28 UTCEPSS rescore
  18. 2026-07-19 02:28 UTCEPSS rescore
  19. 2026-07-18 10:04 UTCEPSS rescore
  20. 2026-07-18 10:04 UTCEPSS rescore
  21. 2026-07-16 17:02 UTCEPSS rescore
  22. 2026-07-16 17:02 UTCEPSS rescore
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 75 more
  1. 2026-07-15 01:59 UTCEPSS rescore
  2. 2026-07-13 06:12 UTCEPSS rescore
  3. 2026-07-12 05:46 UTCEPSS rescore
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 23:24 UTCVendor advisory
  6. 2026-07-11 23:24 UTCGHSA enrichment
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-08 23:46 UTCVendor advisory
  11. 2026-07-08 23:46 UTCGHSA enrichment
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-07-01 09:43 UTCGHSA enrichment
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 23:22 UTCEPSS rescore
  22. 2026-06-30 03:15 UTCVendor advisory
  23. 2026-06-30 03:15 UTCGHSA enrichment
  24. 2026-06-29 14:08 UTCVendor advisory
  25. 2026-06-29 14:08 UTCGHSA enrichment
  26. 2026-06-29 14:06 UTCEPSS rescore
  27. 2026-06-29 14:06 UTCEPSS rescore
  28. 2026-06-28 20:05 UTCVendor advisory
  29. 2026-06-28 20:05 UTCGHSA enrichment
  30. 2026-06-28 14:07 UTCEPSS rescore
  31. 2026-06-28 14:07 UTCEPSS rescore
  32. 2026-06-28 07:25 UTCVendor advisory
  33. 2026-06-28 07:24 UTCGHSA enrichment
  34. 2026-06-28 04:56 UTCEPSS rescore
  35. 2026-06-28 04:56 UTCEPSS rescore
  36. 2026-06-27 18:25 UTCVendor advisory
  37. 2026-06-27 18:25 UTCGHSA enrichment
  38. 2026-06-27 05:45 UTCVendor advisory
  39. 2026-06-27 05:45 UTCGHSA enrichment
  40. 2026-06-27 03:08 UTCEPSS rescore
  41. 2026-06-26 17:03 UTCVendor advisory
  42. 2026-06-26 17:03 UTCGHSA enrichment
  43. 2026-06-26 02:24 UTCVendor advisory
  44. 2026-06-26 02:24 UTCGHSA enrichment
  45. 2026-06-25 13:49 UTCEPSS rescore
  46. 2026-06-25 13:49 UTCEPSS rescore
  47. 2026-06-25 13:29 UTCVendor advisory
  48. 2026-06-25 13:29 UTCGHSA enrichment
  49. 2026-06-25 00:51 UTCVendor advisory
  50. 2026-06-25 00:51 UTCGHSA enrichment
  51. 2026-06-24 14:05 UTCEPSS rescore
  52. 2026-06-24 14:04 UTCEPSS rescore
  53. 2026-06-23 21:32 UTCEPSS rescore
  54. 2026-06-22 14:25 UTCEPSS rescore
  55. 2026-06-22 14:25 UTCEPSS rescore
  56. 2026-06-21 14:56 UTCEPSS rescore
  57. 2026-06-21 14:56 UTCEPSS rescore
  58. 2026-06-21 01:59 UTCEPSS rescore
  59. 2026-06-21 01:59 UTCEPSS rescore
  60. 2026-06-19 19:25 UTCEPSS rescore
  61. 2026-06-19 19:25 UTCEPSS rescore
  62. 2026-06-18 17:52 UTCEPSS rescore
  63. 2026-06-18 17:52 UTCEPSS rescore
  64. 2026-06-17 18:41 UTCVendor advisory
  65. 2026-06-17 18:41 UTCGHSA enrichment
  66. 2026-06-17 17:53 UTCEPSS rescore
  67. 2026-06-17 04:49 UTCVendor advisory
  68. 2026-06-17 04:49 UTCGHSA enrichment
  69. 2026-06-16 17:52 UTCEPSS rescore
  70. 2026-06-16 16:04 UTCVendor advisory
  71. 2026-06-16 16:04 UTCGHSA enrichment
  72. 2026-06-16 02:07 UTCVendor advisory
  73. 2026-06-16 02:07 UTCGHSA enrichment
  74. 2026-06-15 17:48 UTCEPSS rescore
  75. 2026-06-15 13:27 UTCVendor advisory

Frequently asked(5)

What is CVE-2025-70103?
CVE-2025-70103 is a high vulnerability published on May 27, 2026. 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.
When was CVE-2025-70103 disclosed?
CVE-2025-70103 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on May 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-70103 actively exploited?
CVE-2025-70103 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 70.6% of all scored CVEs.
What is the CVSS score of CVE-2025-70103?
CVE-2025-70103 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2025-70103?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-70103, 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

Explore the affected products and dependency analysis for CVE-2025-70103

Explore →

Is Your Infrastructure Affected by CVE-2025-70103?

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