dbcve.org
NavidromeApplication

CVE-2024-41259

CRITICAL · 9.1 CVSS v3.1 Published 2024-08-01
Fix available
A fix is available. Upgrade to after 0.52.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Use of insecure hashing algorithm in the Gravatar's service in Navidrome v0.52.3 allows attackers to manipulate a user's account information.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Navidrome v0.52.3 uses an insecure hashing algorithm (likely MD5, which Gravatar traditionally uses) when integrating with the Gravatar service. This allows attackers to manipulate a user's account information by exploiting the cryptographic weakness.

MitigationUpgrade to a patched version of Navidrome that implements a secure hashing algorithm (e.g., SHA-256) for Gravatar integration, or disable Gravatar integration until a patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NavidromeApplication
Affected:<= 0.52.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Navidrome version
    Run 'navidrome --version' or check the version from the binary/package metadata
    Affected if The installed version is 0.52.3 or lower
  2. Locate Navidrome configuration file
    Find the navidrome.toml or navidrome.conf file, typically in /etc/navidrome/, the application directory, or the user's config directory
    Affected if The configuration file exists and Gravatar settings are present
  3. Verify Gravatar integration status
    In the configuration file, look for 'gravatar' or 'avatar' settings, specifically check if the service is enabled (often a boolean flag like 'enable' or 'enabled')
    Affected if Gravatar integration is enabled in the configuration (the vulnerability only applies when this feature is active)

You are affected if Navidrome version is 0.52.3 or lower AND Gravatar integration is enabled in your configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.52.3
Interim mitigation

Upgrade to a patched version of Navidrome that implements a secure hashing algorithm (e.g., SHA-256) for Gravatar integration, or disable Gravatar integration until a patch is available.

Recommended fix Moderate confidence

0.53.0 or later

  1. Upgrade Navidrome to version 0.53.0 or later, which contains the fix for the insecure Gravatar hashing algorithm vulnerability
Caveat Check release notes for any configuration or database migration requirements between 0.52.3 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Navidrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41259 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-41259 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data