# CVE-2025-44906: Use after free in n/a

> A heap-use-after-free in jhead allows attackers to execute arbitrary code or cause a denial of service via a crafted JPEG file.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 May 2025
- **Updated:** 30 May 2025
- **Also known as:** GHSA-4q97-mrgv-92q2, UBUNTU-CVE-2025-44906, openSUSE-SU-2026:21915-1

## What is CVE-2025-44906?

CVE-2025-44906 is a high-severity use after free vulnerability in n/a, published on 30 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

jhead v3.08 was discovered to contain a heap-use-after-free via the ProcessFile function at jhead.c.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `budgie-backgrounds` | openSUSE:Leap 16.0 | All versions | 3.0-bp160.2.1 |

Products: Jhead Project Jhead.

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

Apply the vendor's patch.

## Is CVE-2025-44906 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-28550](https://insights.sbomify.com/CVE-2022-28550/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-28277](https://insights.sbomify.com/CVE-2021-28277/): Memory corruption in n/a (high 7.8)
- [CVE-2021-28278](https://insights.sbomify.com/CVE-2021-28278/): Memory corruption in n/a (high 7.8)
- [CVE-2021-3496](https://insights.sbomify.com/CVE-2021-3496/): Memory corruption in jhead (high 7.8)
- [CVE-2018-16554](https://insights.sbomify.com/CVE-2018-16554/): Other in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-44906 is a high-severity use after free vulnerability in n/a, published on 30 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-44906 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-44906/ (Markdown: https://insights.sbomify.com/CVE-2025-44906/index.md)
```

## Sources

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

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