CVE-2026-55496
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):
user := v4.Group("user") // protected user group (login required)
user.GET("search",
middleware.RequiredScopes(types.ScopeUserInfoRead),
controllers.FromQueryusersvc.SearchUserService, controllers.UserSearch)
The RequiredScopes check applies to scoped OAuth tokens; plain session requests are not gated by it — so any logged-in user reaches the search.
2. Service — 2-char keyword to SearchActive (service/user/info.go):
type SearchUserService struct { Keyword string form:"keyword" binding:"required,min=2" }
const resultLimit = 10
func (s *SearchUserService) Search(c *gin.Context) ([]*ent.User, error) {
return dep.UserClient().SearchActive(c, resultLimit, s.Keyword)
}
3. The bug — SearchActive has no status predicate (inventory/user.go):
func (c *userClient) SearchActive(ctx context.Context, limit int, keyword string) ([]*ent.User, error) {
ctx = context.WithValue(ctx, LoadUserGroup{}, true)
return withUserEagerLoading(ctx,
c.client.User.Query().
Where(user.Or(user.EmailContainsFold(keyword), user.NickContainsFold(keyword))).
Limit(limit), // <-- no user.StatusEQ(user.StatusActive)
).All(
⚡ Watch CVE-2026-55496
Get an email if CVE-2026-55496 is added to CISA KEV, gains public exploit code, or a new advisory cites it — max one per day, one-click unsubscribe.
Exploitation outlook
- Low exploitation risk0.36% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 29% of all EPSS-scored CVEs.
Advisory coverage (2)
External references
Embed the live status
— this badge updates automatically when the KEV or exploit status changes. How to embed it →
[](https://www.csirts.com/cve/CVE-2026-55496)