# CVE-2025-70103: Memory corruption in n/a

> A heap buffer overflow in libjxl allows attackers to execute arbitrary code or cause denial of service via crafted PBM images.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2026
- **Updated:** 30 May 2026
- **Also known as:** DEBIAN-CVE-2025-70103, ECHO-70e5-ab74-3fec, GHSA-4xm2-q73p-253r, MGASA-2026-0516, OESA-2026-3067, SUSE-SU-2026:22174-1, SUSE-SU-2026:22201-1, SUSE-SU-2026:22210-1, SUSE-SU-2026:2286-1, UBUNTU-CVE-2025-70103, USN-8397-1, openSUSE-SU-2026:10935-1, openSUSE-SU-2026:10955-1, openSUSE-SU-2026:21100-1, openSUSE-SU-2026:21114-1

## What is CVE-2025-70103?

CVE-2025-70103 is a high-severity memory corruption vulnerability in n/a, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2025-70103?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libjxl` | SUSE:Linux Enterprise Server 16.0 | All versions | 0.11.2-160000.2.1 |
| `mozjs128` | SUSE:Linux Enterprise Server 16.0 | All versions | 128.14.0-160000.3.1 |
| `mozjs128` | SUSE:Linux Enterprise Server 16.0 | All versions | 128.14.0-160000.3.1 |
| `libjxl` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 0.11.2-160000.2.1 |
| `mozjs128` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 128.14.0-160000.3.1 |
| `mozjs128` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 128.14.0-160000.3.1 |
| `libjxl` | openSUSE:Leap 16.0 | All versions | 0.11.2-160000.2.1 |
| `libjxl-gtk` | openSUSE:Leap 16.0 | All versions | 0.11.2-160000.2.1 |
| `mozjs128` | openSUSE:Leap 16.0 | All versions | 128.14.0-160000.3.1 |
| `mozjs115` | openSUSE:Tumbleweed | All versions | 115.15.0-9.1 |
| `mozjs140` | openSUSE:Tumbleweed | All versions | 140.10.1-2.1 |

## How do I fix CVE-2025-70103?

Apply the vendor's patch.

## Is CVE-2025-70103 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70103 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-70103 and fix it if it is affected.

What it is: CVE-2025-70103 is a high-severity memory corruption vulnerability in n/a, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70103 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-70103/ (Markdown: https://insights.sbomify.com/CVE-2025-70103/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-70103
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-70103
- OSV: https://osv.dev/vulnerability/CVE-2025-70103

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-70103/
Summaries are generated and may contain mistakes; the official description above is the record.