CVE-2026-123352

HomeBox: API keys are not revoked on password change and never expire by default, so a leaked key survives full credential rotation

Published Nov 17, 2026 CVSS 3.1 · 6.5 Medium EPSS n/a KEV · Not listed
Description
HomeBox is a home inventory and organization system. Prior to 0.27.0, a HomeBox password change revokes the user's other session tokens but does not revoke the user's API keys, and API keys have no default API-key expiration. An attacker who has obtained an API key can therefore retain full API-level access after the account owner changes the password and can keep that access indefinitely unless the owner discovers and manually deletes the key by ID. Because the password change terminates other sessions, the surviving API credential can evade the owner's expected containment and detection. This issue is fixed in version 0.27.0.

Analysis

AI-generated

Technical impact

The vulnerability arises because HomeBox does not revoke API keys when a user changes their password, and the keys never expire by default. An attacker that has recovered a leaked API key can maintain full API‑level access even after the account owner changes the password, because the key continues to be valid. This allows the attacker to read, modify, or delete data stored in HomeBox indefinitely. The weakness is defined as CWE‑1188 and CWE‑613.

Affected Systems

Affected systems are instances of Sysadminsmedia HomeBox running any version earlier than 0.27.0. The documented fix is included in version 0.27.0, which now revokes API keys on password change and introduces a default key expiration policy.

Risk and Exploitability

The CVSS score of 6.5 indicates moderate severity. Exploit likelihood is not quantified by EPSS. The vulnerability is not listed in the CISA KEV catalog. The most probable attack vector requires that the attacker already possesses a valid API key or has discovered a key leak; once that is achieved, no additional privileges are needed to keep access. Thus, the risk to systems that expose API keys and do not rotate them is significant for confidentiality and integrity, especially if keys are leaked through network or storage.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade HomeBox to version 0.27.0 or later to enforce automatic revocation of API keys on password changes and enable key expiration.
  • After the upgrade, revoke all existing API keys and issue fresh keys to trusted users.
  • Implement a policy to rotate API keys regularly and configure automatic expiration to limit the window of opportunity for attackers.

Generated by OpenCVE AI on November 17, 2026 at 20:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Sysadminsmedia
Sysadminsmedia homebox
Vendors & Products Sysadminsmedia
Sysadminsmedia homebox
Type Values Removed Values Added
Description HomeBox is a home inventory and organization system. Prior to 0.27.0, a HomeBox password change revokes the user's other session tokens but does not revoke the user's API keys, and API keys have no default API-key expiration. An attacker who has obtained an API key can therefore retain full API-level access after the account owner changes the password and can keep that access indefinitely unless the owner discovers and manually deletes the key by ID. Because the password change terminates other sessions, the surviving API credential can evade the owner's expected containment and detection. This issue is fixed in version 0.27.0.
Title HomeBox: API keys are not revoked on password change and never expire by default, so a leaked key survives full credential rotation
Weaknesses CWE-1188
CWE-613
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N'}

Weaknesses
  • CWE-1188

    Initialization of a Resource with an Insecure Default

  • CWE-613

    Insufficient Session Expiration

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 17, 2026, 7:43 PM
Reserved
Nov 5, 2026, 8:43 PM
Status
Received
Published
Nov 17, 2026, 8:17 PM
Modified
Nov 17, 2026, 8:17 PM