CVE-2025-48948 — navidrome
Fix: navidrome/navidrome@e543855CVE-2025-48948 is a CWE-863 vulnerability in github.com/navidrome/navidrome. A fix is available for github.com/navidrome/navidrome — see the affected versions and patch details below.
Navidrome Transcoding Permission Bypass Vulnerability Report
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-48948.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
github.com/navidrome/navidromeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
A permission verification flaw in Navidrome allows any authenticated regular user to bypass authorization checks and perform administrator-only transcoding configuration operations, including creating, modifying, and deleting transcoding settings.
Details
Navidrome supports transcoding functionality which, although disabled by default, should restrict configuration operations to administrators only. However, the application fails to properly validate whether a user has administrative privileges when handling transcoding configuration requests.
The vulnerability exists in the API endpoints that manage transcoding settings. When a regular user sends requests to these endpoints, the application processes them without verifying if the user has administrative privileges, despite the JWT token clearly indicating the user is not an administrator ("adm":false).
The affected endpoints include:
POST /api/transcoding(Create transcoding configuration)PUT /api/transcoding/:id(Update transcoding configuration)DELETE /api/transcoding/:id(Delete transcoding configuration)GET /api/transcoding(List transcoding configurations)
PoC
- Set up Navidrome with transcoding enabled
- Log in as a regular user (non-administrator)
- Send the following HTTP request:
POST /api/transcoding HTTP/1.1
Host: 192.168.199.134:4533
Content-Length: 81
x-nd-client-unique-id: e559d130-4295-401e-b65f-be7fdd564e
accept: application/json
x-nd-authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhZG0iOmZhbHNlLCJleHAiOjE3NDY2MzIyNDEsImlhdCI6MTc0NjQ1ODk5NiwiaXNzIjoiTkQiLCJzdWIiOiJ1c2VyMSIsInVpZCI6InV3THJGcWxXNHhnNEt4QjNxMk85eTYifQ.jqv2eESY8QTAHY-oLbBmO0v8IyDXrofvXqQgXSrJ6SM
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.5359.125 Safari/537.36
content-type: application/json
Origin: http://192.168.199.134:4533
Referer: http://192.168.199.134:4533/app/
Accept-Encoding: gzip, deflate
Accept-Language: zh-CN,zh;q=0.9
{"defaultBitRate":192,"name":"trans6","command":"tran6","targetFormat":"tran6"}
- The request will succeed despite the JWT token clearly indicating the user is not an administrator (
"adm":false) - The same operation can be performed with administrator credentials, confirming that no authorization check is being performed
Impact
This vulnerability allows regular users to modify critical system configurations that should be restricted to administrators only. While Navidrome does not recommend enabling transcoding in production environments, when it is enabled, proper authorization checks should still be enforced.
The security impact includes:
- Privilege Escalation: Regular users can perform administrator-only actions
- System Configuration Tampering: Unauthorized users can modify transcoding settings, potentially affecting system performance or functionality
- Potential Command Injection: Since transcoding settings include command parameters, this could potentially lead to command injection if not properly sanitized
In the threat model where administrators are trusted but regular users are not, this vulnerability represents a significant security risk when transcoding is enabled.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/navidrome/navidrome | all versions | 0.56.0go get github.com/navidrome/navidrome@v0.56.0 |
Affected Products
navidromenavidromeDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/navidrome/navidrome, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/navidrome/navidrome to 0.56.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48948 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2025-48948 in your dependencies?
Find it across Go, including transitive dependencies.