# CVE-2026-25579: Navidrome affected by Denial of Service and disk exhaustion via oversized `size` parameter in `/rest/getCoverArt` and `/share/img/` endpoints > Authenticated users can crash the Navidrome server or exhaust disk space by requesting oversized cover art images. - **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 4 Feb 2026 - **Updated:** 5 Feb 2026 - **Also known as:** GHSA-hrr4-3wgr-68x3, GO-2026-4411 ## What is CVE-2026-25579? CVE-2026-25579 is a critical denial of service vulnerability in navidrome, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Navidrome is an open source web-based music collection server and streamer. Prior to version 0.60.0, authenticated users can crash the Navidrome server by supplying an excessively large size parameter to /rest/getCoverArt or to a shared-image URL (/share/img/). When processing such requests, the server attempts to create an extremely large resized image, causing uncontrolled memory growth. This triggers the Linux OOM killer, terminates the Navidrome process, and results in a full service outage. If the system has sufficient memory and survives the allocation, Navidrome then writes these extremely large resized images into its cache directory, allowing an attacker to rapidly exhaust server disk space as well. This issue has been patched in version 0.60.0. Weakness: CWE-789 (Memory Allocation with Excessive Size Value), CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2026-25579? 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-25579? Upgrade github.com/navidrome/navidrome to 0.60.0 or later. ## Is CVE-2026-25579 being exploited? There is no known exploitation of CVE-2026-25579 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-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) - [CVE-2025-48948](https://insights.sbomify.com/CVE-2025-48948/): Navidrome Transcoding Permission Bypass Vulnerability Report (high 7.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-25579 and fix it if it is affected. What it is: CVE-2026-25579 is a critical denial of service vulnerability in navidrome, published on 4 Feb 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-25579 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-25579/ (Markdown: https://insights.sbomify.com/CVE-2026-25579/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25579 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25579 - OSV: https://osv.dev/vulnerability/CVE-2026-25579 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-25579/ Summaries are generated and may contain mistakes; the official description above is the record.