HomeBox: Email Case-Sensitivity Bypass Allows Duplicate Account Creation and Login Denial of Service
- Exploited
- No known exploitation
- Fix
- Fixed in 0.27.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.27.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 24/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
HomeBox, a home inventory and organization system, has a flaw in how it handles email addresses: registration treats differently cased versions of an email as separate accounts, while login does not. An attacker can reach this remotely, without logging in, by registering a differently cased variant of a victim's email, which can lock the victim out of their account and bypass the one-account-per-email rule.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
HomeBox is a home inventory and organization system. Prior to 0.27.0, POST /api/v1/users/register and the users.email uniqueness constraint treat email addresses as case-sensitive while HomeBox uses a case-insensitive login lookup. An unauthenticated attacker who knows a victim's email can register a differently cased variant, creating duplicate rows that cause login to return 401 for both variants and deny the victim access, while also bypassing the one-account-per-email policy. This issue is fixed in version 0.27.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 69 if added to CISA KEV
- Would score about 64 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.27.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- sysadminsmedia homebox
fixed in 0.27.0
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-85287
Is CVE-2026-85287 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-85287?
homebox: before 0.27.0.Source: cve.now feed data
How do I fix CVE-2026-85287?
Upgrade to a fixed version: 0.27.0.Source: cve.now feed data