CVE-2025-70103

HIGHNVD 7.37.3
EchelonGraph scoreMEDIUM confidence

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

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, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2025-209978 (ENISA EUVD) · GHSA-4xm2-q73p-253r (GitHub Security Advisories)Source: ENISA EUVD

7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.3Exploit: No code on recordExposed services: Not assessed

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.3HIGHmedium confidence
EG Risk
64
EG Risk 64/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.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
37th
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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

May 27, 2026

Last Modified

October 12, 2026

Advisory Details (5)

Auto-updated May 30, 2026
Patch available. Sources: github_pr.
Web page

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
Web page

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
Web page

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

https://infosec.exchange/@sigdevel/116642233929409910
Web page

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

https://github.com/sigdevel/pocs/blob/main/res/libjxl/2025/2
GitHub pull request

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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibjxl0.11 (0.11.1-6ubuntu4.2) @ resolute2026-10-27ubuntu

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)
PackageVulnerable rangeFix by version rangeDependents
jpeg-xl0.10.3-1 ... 0.9.2-9 (57 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jpeg-xl0.11.1-4, 0.11.1-5, 0.11.1-6, 0.11.2-0.1~deb13u1
  • every version up to 0.11.2-0.1~deb13u2: fixed in 0.11.2-0.1~deb13u2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jpeg-xl0.11.1-4 ... 0.11.2-5 (12 versions)
  • every version up to 0.11.2-5.1: fixed in 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 11× in last 7d / 44× 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.

Showing the most recent 99 of 357 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 258 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-70103?
CVE-2025-70103 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2025-70103 published?
The CVE record for CVE-2025-70103 was published on May 27, 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 12, 2026; the record at its source may have been updated since.
Is CVE-2025-70103 actively exploited?
CVE-2025-70103 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-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?
A fix for CVE-2025-70103 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-70103 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-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.