# CVE-2026-26828: Null dereference in n/a

> Attackers can cause a Denial of Service in owntone-server by sending a crafted DAAP request that triggers a NULL pointer dereference.

- **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:** Yes
- **Published:** 23 Mar 2026
- **Updated:** 23 Mar 2026
- **Also known as:** GHSA-rfmm-m252-pwvm

## What is CVE-2026-26828?

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

### Official description

A NULL pointer dereference in the daap_reply_playlists function (src/httpd_daap.c) of owntone-server commit 3d1652d allows attackers to cause a Denial of Service (DoS) via sending a crafted DAAP request to the server

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-26828?


## How do I fix CVE-2026-26828?

Apply the vendor's patch.

## Is CVE-2026-26828 being exploited?

There is no known exploitation of CVE-2026-26828 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-26828 and fix it if it is affected.

What it is: CVE-2026-26828 is a high-severity vulnerability in n/a, published on 23 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-26828 in the wild and no public exploit code.

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-2026-26828/ (Markdown: https://insights.sbomify.com/CVE-2026-26828/index.md)
```

## Sources

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

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