CVE-2026-123352 json
HomeBox: API keys are not revoked on password change and never expire by default, so a leaked key survives full credential rotation
published last mo. modified 15h ago also GHSA-59cq-p2m6-hh23 , EUVD-2026-127372
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository sysadminsmedia/homebox. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Is CVE-2026-123352 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N |
Affected products
- sysadminsmedia homebox
Classification
References
Sources
- CVE List CVE-2026-123352
- NVD CVE-2026-123352
- Maintainer advisory GHSA-59cq-p2m6-hh23
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of sysadminsmedia/homebox published their own advisory on GitHub. Reviewed sources take precedence over it.