Advisory record · GHSA-8r7f-r8hj-r3rv

Cloudreve: Information Exposure in `GET /api/v4/user/search`: `SearchActive` omits the active-status predicate, leaking inactive/banned account emails

CVSS 4.3 MediumEPSS 0.0036 · 30th percentile

Published by the GitHub Advisory Database at 24 Jul 2026, 20:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/cloudreve/Cloudreve/v4Go<4.0.0-20260613023921-7e1289d552794.0.0-20260613023921-7e1289d55279
github.com/cloudreve/Cloudreve/v3Go<=3.0.0-20250225100611-da4e44b77af4No fixed version yet
Identifiers
GHSA-8r7f-r8hj-r3rv · CVE-2026-55496 · GO-2026-6098
Weakness (CWE)
CWE-200 · CWE-359
Published
24 Jul 2026
Updated
18 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Cloudreve v4 versions before 4.0.0-20260613023921-7e1289d55279 and Cloudreve v3 versions up to and including 3.0.0-20250225100611-da4e44b77af4 are affected. Any logged-in user can call the user search endpoint, which returns email addresses and profile details for inactive and banned accounts that active-user lookups should hide. Upgrade Cloudreve v4 to 4.0.0-20260613023921-7e1289d55279 or later; no fixed version is listed for v3.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0036, the 30th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:51 UTC First seen by agentprime
  2. 31 Oct 2026, 14:51 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.