CVE-2025-70103: libjxl · Heap Buffer Overflow
Affects libjxlSource CVE Database V5
Not known to be exploited · CVSS 7.3 High.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHublibjxl/libjxlpkg:github/libjxl/libjxlOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, it is recommended to avoid processing untrusted PBM images with libjxl 0.12.0 or to apply any temporary mitigations provided by the vendor once available.
Description
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.
References
- github.com/libjxl/libjxl/issues/4337 (opens in a new tab)
- github.com/libjxl/libjxl/pull/4338 (opens in a new tab)
- github.com/sigdevel/pocs/blob/main/res/libjxl/2025/2 (opens in a new tab)
- infosec.exchange/@sigdevel/116642233929409910 (opens in a new tab)
- openwall.com/lists/oss-security/2026/05/30/7 (opens in a new tab)