Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.3amended

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

CVE-2026-55496GHSA-8r7f-r8hj-r3rv

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Go github.com/cloudreve/Cloudreve/v3

    Affected
    <= 3.0.0-20250225100611-da4e44b77af4
    Fixed in
    no fixed version recorded

  • Go github.com/cloudreve/Cloudreve

    Affected
    every version
    Fixed in
    no fixed version recorded

  • Go github.com/cloudreve/Cloudreve/v4

    Affected
    < 4.0.0-20260613023921-7e1289d55279
    Fixed in
    4.0.0-20260613023921-7e1289d55279

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-55496: 0.36% estimated exploitation activity in the next 30 days; percentile 29.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary GET /api/v4/user/search is available to any logged-in user. 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. A normal logged-in user can therefore enumerate and retrieve the email (plus nickname, avatar, creation time, redacted group, profile share-visibility) of inactive and banned accounts that an active-user directory is supposed to suppress. No global status interceptor compensates — the only User query interceptor is soft-delete, and inactive/banned rows are not soft-deleted. Details Root cause (verified at 26b6b10) 1. Route — logged-in + UserInfo.Read scope (routers/router.go): The RequiredScopes check applies to scoped OAuth tokens; plain session requests are not gated by it — so any…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-8r7f-r8hj-r3rv

  2. Revision 1 · created ·

    Published from osv record GO-2026-6098

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55496

Advisory: Cloudreve: Information Exposure in `GET /api/v4/user/search`: `SearchActive` omits the active-status predicate, leaking inactive/banned account emails
IDs: CVE-2026-55496, GHSA-8r7f-r8hj-r3rv
Record: https://patchnext.com/advisories/cve-2026-55496 (revision 2, source checked 26 Oct 2026, 15:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/cloudreve/Cloudreve/v4 4.0.0-20260613023921-7e1289d55279. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/cloudreve/Cloudreve/v3: affected <= 3.0.0-20250225100611-da4e44b77af4
- Go github.com/cloudreve/Cloudreve: affected every version
- Go github.com/cloudreve/Cloudreve/v4: affected < 4.0.0-20260613023921-7e1289d55279; fixed in 4.0.0-20260613023921-7e1289d55279

## Suggested inspection (read-only)
- Go github.com/cloudreve/Cloudreve/v3: check the installed version with your package manager.
- Go github.com/cloudreve/Cloudreve: check the installed version with your package manager.
- Go github.com/cloudreve/Cloudreve/v4: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/cloudreve/Cloudreve/v3, github.com/cloudreve/Cloudreve, github.com/cloudreve/Cloudreve/v4.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6098 (OSV record GO-2026-6098 lists affected ranges: Go github.com/cloudreve/Cloudreve >=0; Go github.com/cloudreve/Cloudreve/v3 >=0; Go github.com/cloudreve/Cloudreve/v4 >=0 <4.0.0-20260613023921-7e1289d55279 (fixed))
- Verified: https://github.com/advisories/GHSA-8r7f-r8hj-r3rv (GitHub-reviewed advisory GHSA-8r7f-r8hj-r3rv lists affected ranges: Go github.com/cloudreve/Cloudreve/v4 >=0 =0 <=3.0.0-20250225100611-da4e44b77af4)

Commands are suggestions: review each one before running it.

Loading voting…