Navidrome allows an authentication bypass in Subsonic API with non-existent username

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-27112: 0.98% estimated exploitation activity in the next 30 days; percentile 62.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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: 2. Calculate the MD5 hash of an empty password plus the salt: 3. Send a request specifying a fake user, with the hash and salt values: 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…

Published by the source

25 Feb 2025, 17:49 UTC

Last modified by the source

25 Feb 2025, 17:49 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c3p4-vm8f-386p

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-27112

Advisory: Navidrome allows an authentication bypass in Subsonic API with non-existent username
IDs: CVE-2025-27112, GHSA-c3p4-vm8f-386p
Record: https://patchnext.com/advisories/cve-2025-27112 (revision 1, source checked 26 Oct 2026, 15:08 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/navidrome/navidrome 0.54.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/navidrome/navidrome: affected >= 0.52.0, < 0.54.5; fixed in 0.54.5

## Suggested inspection (read-only)
- Go github.com/navidrome/navidrome: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/navidrome/navidrome.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c3p4-vm8f-386p (GitHub-reviewed advisory GHSA-c3p4-vm8f-386p lists affected ranges: Go github.com/navidrome/navidrome >=0.52.0 <0.54.5)

Commands are suggestions: review each one before running it.