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

> Remote attackers can crash the owntone-server via a null pointer dereference in the DACP reply function, causing denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2026
- **Updated:** 21 Jan 2026
- **Also known as:** GHSA-6j26-jfmq-hf5r

## What is CVE-2025-57156?

CVE-2025-57156 is a high-severity vulnerability in n/a, published on 20 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NULL pointer dereference in the dacp_reply_playqueueedit_clear function in src/httpd_dacp.c in owntone-server through commit 6d604a1 (newer commit after version 28.12) allows remote attackers to cause a Denial of Service (crash).

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Owntone Owntone Server.

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

No fix has been published for CVE-2025-57156 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-57156 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-38383](https://insights.sbomify.com/CVE-2021-38383/): Use after free in n/a (critical 9.8)
- [CVE-2025-57155](https://insights.sbomify.com/CVE-2025-57155/): Null dereference in n/a (high 7.5)
- [CVE-2025-63647](https://insights.sbomify.com/CVE-2025-63647/): Null dereference in n/a (high 7.5)
- [CVE-2025-63648](https://insights.sbomify.com/CVE-2025-63648/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-57156 is a high-severity vulnerability in n/a, published on 20 Jan 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-57156 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-57156/ (Markdown: https://insights.sbomify.com/CVE-2025-57156/index.md)
```

## Sources

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

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