# CVE-2024-41259: Navidrome uses MD5 hashing algorithm

> Attackers can manipulate user account information due to insecure hashing in Gravatar integration, affecting Navidrome music server users.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Aug 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-hrmx-8jjv-g758, GO-2024-3029

## What is CVE-2024-41259?

CVE-2024-41259 is a critical vulnerability in n/a, published on 1 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2024-41259?

3 open source packages ship an affected version, including github.com/navidrome/navidrome. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/navidrome/navidrome` | Go | All versions | None |
| `github.com/navidrome/navidrome` | Go | All versions to 0.52.3 | None |
| `github.com/navidrome/navidrome` | Go | All versions to 0.52.3 | None |

Products: Navidrome Navidrome.

## How do I fix CVE-2024-41259?

No fix has been published for CVE-2024-41259 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-41259 being exploited?

There is no known exploitation of CVE-2024-41259 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-47062](https://insights.sbomify.com/CVE-2024-47062/): Multiple SQL Injections and ORM Leak in navidrome (critical 9.4)
- [CVE-2026-25579](https://insights.sbomify.com/CVE-2026-25579/): Navidrome affected by Denial of Service and disk exhaustion via oversized `size` parameter in `/rest/getCoverArt` and `/share/img/<token>` endpoints (critical 9.2)
- [CVE-2025-48949](https://insights.sbomify.com/CVE-2025-48949/): Navidrome allows SQL Injection via role parameter (high 8.9)
- [CVE-2023-51442](https://insights.sbomify.com/CVE-2023-51442/): Authentication bypass vulnerability in navidrome's subsonic endpoint (high 8.6)
- [CVE-2025-48948](https://insights.sbomify.com/CVE-2025-48948/): Navidrome Transcoding Permission Bypass Vulnerability Report (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41259 and fix it if it is affected.

What it is: CVE-2024-41259 is a critical vulnerability in n/a, published on 1 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41259 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/navidrome/navidrome (Go): affected all versions; no fix listed
- github.com/navidrome/navidrome (Go): affected all versions up to 0.52.3; no fix listed
- github.com/navidrome/navidrome (Go): affected all versions up to 0.52.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-41259/ (Markdown: https://insights.sbomify.com/CVE-2024-41259/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41259
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41259
- OSV: https://osv.dev/vulnerability/CVE-2024-41259

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-41259/
Summaries are generated and may contain mistakes; the official description above is the record.