# CVE-2026-25578: Navidrome is vulnerable to XSS via comment from song metadata

> An attacker can inject malicious scripts via song metadata to steal user credentials from the Navidrome music server.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N`)
- **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:** 4 Feb 2026
- **Updated:** 5 Feb 2026
- **Also known as:** GHSA-rh3r-8pxm-hg4w, GO-2026-4413

## What is CVE-2026-25578?

CVE-2026-25578 is a medium-severity cross-site scripting vulnerability in navidrome, published on 4 Feb 2026. 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

Navidrome is an open source web-based music collection server and streamer. Prior to version 0.60.0, a cross-site scripting vulnerability in the frontend allows a malicious attacker to inject code through the comment metadata of a song to exfiltrate user credentials. This issue has been patched in version 0.60.0.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

3 open source packages ship an affected version, including github.com/navidrome/navidrome. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/navidrome/navidrome` | Go | All versions | 0.60.0 |
| `github.com/navidrome/navidrome` | Go | All versions | 0.60.0 |
| `github.com/navidrome/navidrome` | Go | All versions | 0.60.0 |

Products: Navidrome Navidrome.

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

Upgrade github.com/navidrome/navidrome to 0.60.0 or later.

## Is CVE-2026-25578 being exploited?

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

## Other vulnerabilities in navidrome

- [CVE-2024-47062](https://insights.sbomify.com/CVE-2024-47062/): Multiple SQL Injections and ORM Leak in navidrome (critical 9.4)
- [CVE-2026-25579](https://insights.sbomify.com/CVE-2026-25579/): Navidrome affected by Denial of Service and disk exhaustion via oversized `size` parameter in `/rest/getCoverArt` and `/share/img/<token>` endpoints (critical 9.2)
- [CVE-2024-41259](https://insights.sbomify.com/CVE-2024-41259/): Navidrome uses MD5 hashing algorithm (critical 9.1)
- [CVE-2025-48949](https://insights.sbomify.com/CVE-2025-48949/): Navidrome allows SQL Injection via role parameter (high 8.9)
- [CVE-2023-51442](https://insights.sbomify.com/CVE-2023-51442/): Authentication bypass vulnerability in navidrome's subsonic endpoint (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25578 is a medium-severity cross-site scripting vulnerability in navidrome, published on 4 Feb 2026. 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: There is no known exploitation of CVE-2026-25578 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/navidrome/navidrome (Go): affected all versions; fixed in 0.60.0
- github.com/navidrome/navidrome (Go): affected all versions; fixed in 0.60.0
- github.com/navidrome/navidrome (Go): affected all versions; fixed in 0.60.0

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

## Sources

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

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