ByteStash API Keys Stayed Valid After Account Deactivation (CVE-2026-126658)
A flaw in ByteStash versions 1.5.10 through 1.6.2 lets API keys keep working after the owning account has been deactivated. The API-key validation path does not verify whether the account is still active, so administrators who disable a user may believe access has ended when it has not. Any holder of a surviving key, including a former user, a compromised client, or an automation, could keep reading or modifying stored snippets, which may contain sensitive internal material. The recommended remedy is upgrading to version 1.6.2 and confirming that deactivated keys are rejected, along with auditing and rotating keys and reviewing logs for post-deactivation use. Organizations unable to upgrade immediately should restrict API and MCP access as a temporary measure, since this does not fix the underlying account-status check.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)
Log in to join the discussion and vote.
Log in