CVE-2026-101048: Cloudreve before 4.17.0 SSRF via Admin.Read OAuth scope
Cloudreve before 4.17.0 registers the administrative node test endpoints (POST /api/v4/admin/node/test and POST /api/v4/admin/node/test/downloader) without requiring the Admin.Write OAuth scope, unlike the node create/update/delete routes. An OAuth client that has been authorized by an administrator with only the Admin.Read scope can therefore submit attacker-controlled node definitions and cause the Cloudreve server to issue outbound requests to arbitrary URLs, enabling blind server-side request forgery, internal service probing, and delivery of signed Cloudreve slave-style requests to attacker-chosen endpoints.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Cloudreveto a version that resolves this vulnerability.Fixed in 4.17.0
Event History
Frequently Asked Questions
What level of access does an attacker need?
The attacker needs an OAuth client that an administrator has authorized with the Admin.Read scope. Admin.Write is not required to access the affected node test endpoints.
Which requests can be abused?
The affected endpoints are POST /api/v4/admin/node/test and POST /api/v4/admin/node/test/downloader. They accept attacker-controlled node definitions that can make the Cloudreve server send outbound requests to arbitrary URLs.
What can an attacker do through the SSRF condition?
The issue enables blind server-side request forgery and internal service probing. It can also cause Cloudreve to deliver signed slave-style requests to attacker-selected endpoints.
Which versions are affected?
Cloudreve versions before 4.17.0 are affected. Upgrading to 4.17.0 or later addresses the described scope-enforcement gap.