# CVE-2025-50952: Null dereference in n/a

> A NULL pointer dereference in OpenJPEG allows attackers to cause a denial of service via crafted image files.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Aug 2025
- **Updated:** 29 Dec 2025
- **Also known as:** ALPINE-CVE-2025-50952, BELL-CVE-2025-50952, DEBIAN-CVE-2025-50952, DLA-4424-1, ECHO-726a-4071-0f2f, GHSA-2pr5-qxg3-pfqf, JLSEC-2026-551, OESA-2025-2038, OESA-2025-2039, OESA-2025-2040, OESA-2025-2041, OESA-2025-2042, OESA-2025-2075, UBUNTU-CVE-2025-50952, openSUSE-SU-2025:15430-1

## What is CVE-2025-50952?

CVE-2025-50952 is a medium-severity vulnerability in Uclouvain Openjpeg, published on 7 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

openjpeg v 2.5.0 was discovered to contain a NULL pointer dereference via the component /openjp2/dwt.c.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `texmaker` | openSUSE:Tumbleweed | All versions | 6.0.1-2.1 |

Products: Uclouvain Openjpeg.

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

Upgrade to a fixed version.

## Is CVE-2025-50952 being exploited?

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

## Other vulnerabilities in Uclouvain Openjpeg

- [CVE-2013-4289](https://insights.sbomify.com/CVE-2013-4289/): Integer overflow in n/a (critical 10.0)
- [CVE-2013-4290](https://insights.sbomify.com/CVE-2013-4290/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-3358](https://insights.sbomify.com/CVE-2012-3358/): Memory corruption in n/a (critical 10.0)
- [CVE-2018-7648](https://insights.sbomify.com/CVE-2018-7648/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-17479](https://insights.sbomify.com/CVE-2017-17479/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50952 is a medium-severity vulnerability in Uclouvain Openjpeg, published on 7 Aug 2025. 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-50952 exists.

Affected product: Uclouvain Openjpeg. 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-50952/ (Markdown: https://insights.sbomify.com/CVE-2025-50952/index.md)
```

## Sources

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

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