Description
Cloudreve is a self-hosted file management and sharing system. Prior to 4.17.0, GET /api/v4/user/search calls SearchActive without adding a StatusActive predicate and serializes matches at RedactLevelUser, allowing any logged-in user to enumerate email addresses and profile metadata for inactive or banned accounts. The service calls userClient.SearchActive, but despite its name that method filters only by email/nickname keyword and never adds a StatusActive predicate — while the sibling lookups GetActiveByID and GetActiveByDavAccount, defined a few lines above it, do. Search hits are serialized at RedactLevelUser, which includes the email address. This issue is fixed in version 4.17.0.
Published: 2026-07-31
Score: 4.3 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Cloudreve versions prior to 4.17.0 expose sensitive user profile data, including email addresses and other metadata, for accounts that are inactive or banned. The vulnerability exists in the GET /api/v4/user/search endpoint, which invokes a function named SearchActive but does not apply the required active-status filter. The resulting data set is serialized with a RedactLevel that still contains email addresses, enabling any authenticated user to enumerate private information for accounts that should remain hidden. The flaw triggers a privacy violation classified as CWE-200 and CWE-359.

Affected Systems

The affected product is the Cloudreve self-hosted file management and sharing platform, specifically all releases 4.16.x and earlier. The issue is resolved in release 4.17.0; installations running any newer version are not affected.

Risk and Exploitability

The vulnerability scores a CVSS of 4.3, indicating moderate confidentiality impact without denial-of-service or privilege-escalation effects. The EPSS score is less than 1%, suggesting exploitation is unlikely in the wild, and the flaw is not listed in the CISA KEV catalog. Attackers who can authenticate to the application can exploit the flaw simply by making a /api/v4/user/search request; no additional privileges are required. Because the active-status predicate is omitted, enumeration does not stop at active accounts, potentially exposing dozens of private email addresses.

Generated by OpenCVE AI on August 2, 2026 at 04:38 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Cloudreve to version 4.17.0 or newer.
  • Restrict the /api/v4/user/search endpoint to administrators or remove the endpoint entirely for non-privileged users.
  • Apply temporary access controls that filter out inactive or banned accounts from search results until the upgrade is applied.

Generated by OpenCVE AI on August 2, 2026 at 04:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-8r7f-r8hj-r3rv Cloudreve: Information Exposure in `GET /api/v4/user/search`: `SearchActive` omits the active-status predicate, leaking inactive/banned account emails
History

Fri, 31 Jul 2026 15:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 31 Jul 2026 05:45:00 +0000

Type Values Removed Values Added
First Time appeared Cloudreve
Cloudreve cloudreve
Vendors & Products Cloudreve
Cloudreve cloudreve

Fri, 31 Jul 2026 04:15:00 +0000

Type Values Removed Values Added
Description Cloudreve is a self-hosted file management and sharing system. Prior to 4.17.0, GET /api/v4/user/search calls SearchActive without adding a StatusActive predicate and serializes matches at RedactLevelUser, allowing any logged-in user to enumerate email addresses and profile metadata for inactive or banned accounts. The service calls userClient.SearchActive, but despite its name that method filters only by email/nickname keyword and never adds a StatusActive predicate — while the sibling lookups GetActiveByID and GetActiveByDavAccount, defined a few lines above it, do. Search hits are serialized at RedactLevelUser, which includes the email address. This issue is fixed in version 4.17.0.
Title Cloudreve: Inactive/banned account emails leaked via GET /api/v4/user/search because SearchActive() omits the active-status predicate
Weaknesses CWE-200
CWE-359
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N'}


Subscriptions

Cloudreve Cloudreve
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-07-31T14:02:34.248Z

Reserved: 2026-06-16T22:28:27.062Z

Link: CVE-2026-55496

cve-icon Vulnrichment

Updated: 2026-07-31T13:59:02.705Z

cve-icon NVD

Status : Received

Published: 2026-07-31T04:17:22.877

Modified: 2026-07-31T14:16:50.340

Link: CVE-2026-55496

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-02T04:45:15Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-359

    Exposure of Private Personal Information to an Unauthorized Actor