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.
CVE-2026-55496
This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(medium)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
July 24, 2026
Last Modified
July 31, 2026
Advisory Details (3)
Auto-updated Jul 31, 2026Information Exposure in `GET /api/v4/user/search`: `SearchActive` omits the active-status predicate, leaking inactive/banned account emails · Advisory · cloudreve/cloudreve · GitHub
https://github.com/cloudreve/cloudreve/security/advisories/GHSA-8r7f-r8hj-r3rv4.17.0
Patch available: cloudreve/cloudreve 4.17.0
https://github.com/cloudreve/cloudreve/releases/tag/4.17.0commit 7e1289d55279 (cloudreve/cloudreve)
Fix landed in cloudreve/cloudreve commit 7e1289d55279 — awaiting tagged release
https://github.com/cloudreve/cloudreve/commit/7e1289d552794bdbeb551be78456115c87dcb3daVendor Advisories for CVE-2026-55496(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 1 ecosystem)
Go(2)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/cloudreve/Cloudreve/v3 | — | — | — |
| github.com/cloudreve/Cloudreve/v4 | — | 4.0.0-20260613023921-7e1289d55279 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 49× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-25 23:32 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 01:00 UTCEG score recompute
- 2026-08-23 03:28 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 04:56 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 06:23 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 07:51 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 09:19 UTCEG score recompute
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 10:47 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 12:14 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 13:41 UTCEG score recompute
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 15:09 UTCEG score recompute
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 16:36 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 19:26 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
Show 26 moreShow fewer
- 2026-08-11 20:54 UTCEG score recompute
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-09 23:50 UTCEG score recompute
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 01:18 UTCEG score recompute
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 02:45 UTCEG score recompute
- 2026-08-07 04:13 UTCEG score recompute
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 05:41 UTCEG score recompute
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 07:10 UTCEG score recompute
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-04 08:35 UTCEG score recompute
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 11:29 UTCEG score recompute
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 12:57 UTCEG score recompute
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-31 14:25 UTCEG score recompute
- 2026-07-31 14:09 UTCEG score recompute
- 2026-07-31 04:20 UTCEG score recompute
- 2026-07-31 02:30 UTCEG score recompute
- 2026-07-27 08:15 UTCEG score recompute
- 2026-07-24 21:13 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-55496?
When was CVE-2026-55496 disclosed?
Is CVE-2026-55496 actively exploited?
What is the CVSS score of CVE-2026-55496?
How do I remediate CVE-2026-55496?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55496
Is Your Infrastructure Affected by CVE-2026-55496?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.