CVE-2026-85286 · Package
NO FIX YET · SEE WHAT TO DO
HomeBox, a self-hosted home inventory app, answers login attempts for unknown usernames faster than for real ones because it skips the password-hash check. An unauthenticated remote attacker can use the response timing to find which email addresses have accounts.
first public Oct 17, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running HomeBox before 0.27.0 with the login endpoint reachable by others, such as a shared or internet-facing instance. The impact is limited to confirming which email addresses have accounts, so private single-user instances on a closed network are lower risk. The sources do not describe further conditions.
Not affected if closed-network, version-0.27.0-or-later
Who cares homebox, login, self-hosted
0.27.0 are affected./api/v1/users/login.0.27.0 or later.HomeBox is a home inventory and organization system. Prior to 0.27.0, the POST /api/v1/users/login endpoint performs password-hash verification only when the submitted username matches an existing account, while unknown usernames return immediately. Although both paths return the same 401 unauthorized response, the processing-time discrepancy allows an unauthenticated remote attacker to distinguish registered email addresses; rate limiting only reduces the number of attempts per window. This issue is fixed in version 0.27.0.
This page as .md ·
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.