Navidrome Stores JWT Secret in Plaintext in navidrome.db

Exploitation

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

CVSS

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

EPSS

• CVE-2024-56362: 0.15% estimated exploitation activity in the next 30 days; percentile 4.51 (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.

Navidrome stores the JWT secret in plaintext in the navidrome.db database file under the property table. This practice introduces a security risk because anyone with access to the database file can retrieve the secret. The JWT secret is critical for the authentication and authorization system. If exposed, an attacker could: - Forge valid tokens to impersonate users, including administrative accounts. - Gain unauthorized access to sensitive data or perform privileged actions. This vulnerability has been tested on the latest version of Navidrome and poses a significant risk in environments where the database file is not adequately secured.

Published by the source

23 Dec 2024, 20:17 UTC

Last modified by the source

15 Jan 2025, 20:47 UTC

Source last checked

26 Oct 2026, 15:08 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-xwx7-p63r-2rj8

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

# Patch Next advisory brief: CVE-2024-56362

Advisory: Navidrome Stores JWT Secret in Plaintext in navidrome.db
IDs: CVE-2024-56362, GHSA-xwx7-p63r-2rj8
Record: https://patchnext.com/advisories/cve-2024-56362 (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: High (CVSS 7.1)
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.1. A vendor fix does not mean a deployment is fixed.

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

## 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-xwx7-p63r-2rj8 (GitHub-reviewed advisory GHSA-xwx7-p63r-2rj8 lists affected ranges: Go github.com/navidrome/navidrome >=0 <=0.53.3)

Commands are suggestions: review each one before running it.