# CVE-2026-41457: OwnTone Server < 29.1 SQL Injection via query and filter Parameters

> Attackers can inject SQL via DAAP query parameters to bypass filters and access unauthorized media library data in OwnTone Server.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Apr 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-6742-w24p-5jgf

## What is CVE-2026-41457?

CVE-2026-41457 is a medium-severity SQL injection vulnerability in owntone-server, published on 22 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OwnTone Server versions 28.4 through 29.0 contain a SQL injection vulnerability in DAAP query and filter handling that allows attackers to inject arbitrary SQL expressions by supplying malicious values through the query= and filter= parameters for integer-mapped DAAP fields. Attackers can exploit insufficient sanitization of these parameters to bypass filters and gain unauthorized access to media library data.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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


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

Upgrade to a fixed version.

## Is CVE-2026-41457 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41457 is a medium-severity SQL injection vulnerability in owntone-server, published on 22 Apr 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-41457 in the wild and no public exploit code.

Affected product: owntone-server. 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-41457/ (Markdown: https://insights.sbomify.com/CVE-2026-41457/index.md)
```

## Sources

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

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