Authentication bypass vulnerability in navidrome's subsonic endpoint

Exploitation

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

CVSS

8.6 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

EPSS

• CVE-2023-51442: 0.69% estimated exploitation activity in the next 30 days; percentile 52.85 (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 A security vulnerability has been identified in navidrome's subsonic endpoint, allowing for authentication bypass. This exploit enables unauthorized access to any known account by utilizing a JSON Web Token (JWT) signed with the key "not so secret". The vulnerability can only be exploited on instances that have never been restarted. Details Navidrome supports an extension to the subsonic authentication scheme, where a JWT can be provided using a jwt query parameter instead of the traditional password or token and salt (corresponding to resp. the p or t and s query parameters). During the first initialization, navidrome generates a random key that is then used by the authentication module to validate JWTs before extracting the username from the sub claim. If for some reason the key cannot be retrieved by the initialization code, a hardcoded value is used instead: "not so secret". A bug in the order of operations during navidrome startup results in the authentication module…

Published by the source

19 Dec 2023, 23:37 UTC

Last modified by the source

21 Dec 2023, 15:58 UTC

Source last checked

26 Oct 2026, 15:03 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-wq59-4q6r-635r

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

# Patch Next advisory brief: CVE-2023-51442

Advisory: Authentication bypass vulnerability in navidrome's subsonic endpoint
IDs: CVE-2023-51442, GHSA-wq59-4q6r-635r
Record: https://patchnext.com/advisories/cve-2023-51442 (revision 1, source checked 26 Oct 2026, 15:03 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.6)
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.50.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/navidrome/navidrome: affected <= 0.50.1; fixed in 0.50.2

## 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-wq59-4q6r-635r (GitHub-reviewed advisory GHSA-wq59-4q6r-635r lists affected ranges: Go github.com/navidrome/navidrome >=0 <=0.50.1)

Commands are suggestions: review each one before running it.