CVE-2026-48974: HomeBox: Forced Group Membership Without Consent in Homebox AddMember Handler

Published Sep 21, 2026
·
Updated

HomeBox is a home inventory and organization system. Prior to 0.26.0, POST /v1/groups/members invokes HandleGroupMemberAdd and GroupService.AddMember using a caller-supplied userID without requiring an owner role, an invitation token, target-user consent, or target-user notification. Any authenticated user can force another account into the caller's group, disclose the target user's email address and name through the resulting member list, and create the membership prerequisite used by a separate cross-group inventory-wipe vulnerability. This issue is fixed in version 0.26.0.

Affected Software

1 affected component
HomeBox<0.26.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade HomeBox to a version that resolves this vulnerability.

    Fixed in 0.26.0

Event History

Sep 21, 2026
CVE Published
via MITRE·05:42 PM
Data Sourced
via MITRE·05:42 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue, and what access do they need?

Any authenticated HomeBox user can exploit it. The attacker only needs to submit a request to the group-member addition endpoint with another account's user ID; owner privileges, an invitation token, and the target user's consent are not required.

2

What information or impact can result from exploitation?

An attacker can force a target account into the attacker's group and then obtain the target user's email address and name from the resulting member list. The unauthorized membership can also satisfy a prerequisite for a separate cross-group inventory-wipe vulnerability.

3

Are users protected by default from unwanted group additions?

No. In affected versions, the add-member handler does not require an owner role, invitation token, target-user consent, or target-user notification.

4

How can I determine whether my deployment is affected?

HomeBox versions earlier than 0.26.0 are affected. Review group membership changes for accounts added without consent, particularly where the adding user was not a group owner or no invitation process was used.

5

What should I do if I cannot upgrade immediately?

The provided information identifies version 0.26.0 as the fix but does not specify a workaround. Until upgrading, treat authenticated users as able to add arbitrary accounts to their groups and monitor or restrict access to the affected endpoint where possible.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203