EUVD-2026-23539Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Lifecycle Timeline
7DescriptionGitHub Advisory
HomeBox is a home inventory and organization system. Versions prior to 0.25.0 contain a vulnerability where the defaultGroup ID remained permanently assigned to a user after being invited to a group, even after their access to that group was revoked. While the web interface correctly enforced the access revocation and prevented the user from viewing or modifying the group's contents, the API did not. Because the original group ID persisted as the user's defaultGroup, and this value was not properly validated when the X-Tenant header was omitted, the user could still perform full CRUD operations on the group's collections through the API, bypassing the intended access controls. This issue has been fixed in version 0.25.0.
AnalysisAI
Broken access control in HomeBox prior to 0.25.0 allows authenticated users with revoked group access to continue performing full CRUD operations via API. After group invitation revocation, the defaultGroup ID persists on the user object, and when API requests omit the X-Tenant header, this unvalidated value enables bypassing access controls to read, modify, and delete group inventory data. Web interface correctly enforces revocation, creating a dangerous inconsistency. No active exploitation confirmed (EPSS data unavailable), but the authentication bypass tag and CVSS 8.1 with network vector indicate significant risk for multi-tenant HomeBox deployments.
Technical ContextAI
HomeBox is a home inventory and organization system (cpe:2.3:a:sysadminsmedia:homebox) with multi-tenant group functionality. The vulnerability stems from CWE-708 (Incorrect Ownership Assignment), where user identity management fails during group access revocation. The system uses a defaultGroup field on user objects and an X-Tenant header for API tenant isolation. When users are invited to groups, defaultGroup is set but never cleared upon revocation. The API's tenant validation logic improperly trusts this persisted defaultGroup value when X-Tenant is absent, treating it as an implicit authorization. This creates a privilege escalation path where revoked users retain API-level access while UI-level controls function correctly, indicating inconsistent authorization enforcement across application layers.
RemediationAI
Upgrade to HomeBox version 0.25.0 or later, which fixes the defaultGroup persistence and X-Tenant validation issues. Release information is at https://github.com/sysadminsmedia/homebox/releases/tag/v0.25.0. If immediate upgrade is not feasible, implement API gateway-level enforcement requiring X-Tenant header on all API requests and rejecting requests without it (this prevents the vulnerable code path but may break legitimate client applications expecting implicit tenant context). Alternatively, conduct audit of all users with revoked group access and manually clear their defaultGroup field through database manipulation, though this is error-prone and doesn't address the underlying validation gap. For high-security environments, disable multi-tenant group features entirely until upgrade is completed. All workarounds have operational impact and should be considered temporary measures.
Homebox prior to version 0.24.0 fails to validate the TrustProxy configuration setting, allowing attackers to bypass aut
Homebox prior to 0.24.0-rc.1 allows authenticated users to trigger HTTP POST requests to arbitrary destinations through
Stored XSS in Homebox prior to 0.24.0-rc.1 allows authenticated users to upload malicious HTML or SVG files containing e
Same weakness CWE-708 – Incorrect Ownership Assignment
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today