What’s Vulnerable › Vulnerabilities

CVE-2026-55496: Cloudreve: Inactive/banned account emails leaked via GET /api/v4/user/search because SearchActive() omits the active-status predicate

• Severity: medium (CVSS 4.3 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.4% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-07-31 · updated 2026-09-08
• Weakness: CWE-200

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.

Affected products

• cloudreve: 4.17.0

References

• https://github.com/cloudreve/cloudreve/commit/7e1289d552794bdbeb551be78456115c87dcb3da
• https://github.com/cloudreve/cloudreve/releases/tag/4.17.0
• https://github.com/cloudreve/cloudreve/security/advisories/GHSA-8r7f-r8hj-r3rv
• https://github.com/cloudreve/cloudreve/security/advisories/GHSA-8r7f-r8hj-r3rv

Get alerted when CVE-2026-55496 or the next vulnerability affects your stack