CVE-2026-25579: Github.com/navidrome/navidrome Denial of Service Vulnerability
CRITICALCVE-2026-25579 is a CRITICAL denial of service vulnerability (CWE-789: Memory Allocation with Excessive Size Value) affecting Github.com/navidrome/navidrome libraries in the Go ecosystem. The issue involves navidrome affected by denial of service and disk exhaustion via oversized `size` parameter in `/rest/getcoverart` and `/share/img/<token>` endpoints. Remediation is available by upgrading affected packages to version 0.60.0.
CVE-2026-25579 at a Glance
How to Fix CVE-2026-25579
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-25579, 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-789: Memory Allocation with Excessive Size Value, where the product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated. 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-25579 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-25579?
Which Github.com/navidrome/navidrome versions are affected?
What version fixes CVE-2026-25579?
Is github.com/navidrome/navidrome affected?
What CWE is associated with CVE-2026-25579?
How can I check Go dependencies for CVE-2026-25579?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-hrr4-3wgr-68x3",
"modified" : "2026-02-05T00:37:07Z",
"published" : "2026-02-04T00:14:02Z",
"aliases" : [ "CVE-2026-25579" ],
"summary" : "Navidrome affected by Denial of Service and disk exhaustion via oversized `size` parameter in `/rest/getCoverArt` and `/share/img/<token>` endpoints",
"details" : "### Summary\nAuthenticated users can crash the Navidrome server by supplying an excessively large `size` parameter to `/rest/getCoverArt` or to a shared-image URL (`/share/img/<token>`). 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.\n\nIf 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.\n\n### Details\nBoth `/rest/getCoverArt` and `/share/img/<token>` accept a `size` parameter that is passed directly into the image processing routine without any upper bound validation. When a very large integer is provided, Navidrome attempts to generate a resized image of that size. This leads to excessive memory allocation inside the image resizing path.\n\nIn the `/rest/getCoverArt` handler, the value is read as:\n\n```go\nsize := p.IntOr(\"size\", 0)\nimgReader, lastUpdate, err := api.artwork.GetOrPlaceholder(ctx, id, size, square)\n```\n\nBecause no limit is enforced, the image subsystem receives the supplied value as-is. When the requested size is extremely large, the process consumes large amounts of RAM until it is killed by the kernel's OOM killer. If the system has enough available memory to complete the resize operation, the resulting oversized image is then written to Navidrome's cache directory, which can quickly fill the server's disk.\n\nThe same behavior is reachable through `/share/img/<token>` as long as the attacker possesses a valid sharing token.\n\n### PoC\n1. Authenticate normally to obtain access to `/rest/getCoverArt` or a valid sharing link containing a `/share/img/<token>` URL.\n2. Send a regular request with a small size value, for example:\n\n```\n/rest/getCoverArt?...&size=300&square=true\n```\n\n3. Replace the `size` parameter with a very large number, such as:\n\n```\n/rest/getCoverArt?...&size=300000&square=true\n```\n\n4. The server rapidly allocates memory while attempting to create an oversized image. This leads to the Navidrome process being terminated by the OOM killer.\n5. The same behavior can be reproduced with a valid shared-image link:\n\n```\n/share/img/<token>?size=300000&square=true\n```\n\nIf the system does not run out of memory, the oversized resized image is written to the cache directory, causing disk usage to grow quickly.\n\n### Impact\nSupplying an excessively large `size` parameter to `/rest/getCoverArt` or `/share/img/<token>` allows any authenticated user to trigger a Denial of Service condition. During image resizing, the server attempts to allocate extremely large amounts of memory, which can cause not only Navidrome itself to be terminated by the OOM killer, but in some configurations may also destabilize or crash the entire host system.\n\nOn systems with sufficient memory, the oversized resized images are written to Navidrome's cache directory instead, allowing an attacker to rapidly consume all available disk space. This leads to a second form of Denial of Service, where the host becomes unable to write logs, operate dependent services, or perform basic system tasks due to storage exhaustion.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "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"
} ],
"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-hrr4-3wgr-68x3"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-25579"
}, {
"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-400", "CWE-770", "CWE-789" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-02-04T00:14:02Z",
"nvd_published_at" : "2026-02-04T22:16:01Z"
}
}