CVE-2026-126658
Medium 5.3No known exploitationFix status unknownTitle not yet published
Record last updated
CVSS score
5.3
Medium on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
0.2%
Higher than 16% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
None
Not in the KEV catalog
Description
ByteStash 1.5.10 before 1.6.2 contains an insufficient session expiration vulnerability that allows holders of API keys to keep access after account deactivation because validateApiKey never checks account status. Attackers holding a deactivated account's API key can read, create, modify and delete its snippets via /api/snippets and use every MCP tool via /mcp.
Weakness: CWE-613
Patching and mitigation
- Patch status
- Unknown: no source documents a fix
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
No affected products documented yet.
Timeline
- No dated events documented yet.
Vendor guidance and references
- https://github.com/jordan-dalby/ByteStash/blob/v1.6.1/server/src/repositories/apiKeyRepository.js (opens in a new tab)
- https://github.com/jordan-dalby/ByteStash/commit/eb4ecdfc30f2e7d1424137fa7fe3a9eed663218b (opens in a new tab)
- https://github.com/jordan-dalby/ByteStash/releases/tag/v1.6.2 (opens in a new tab)
- https://github.com/jordan-dalby/ByteStash/security/advisories/GHSA-26m9-ww2j-3cr5 (opens in a new tab)
- https://notes.netbytesec.com/2026/11/cve-2026-126658-bytestash-1510-before.html (opens in a new tab)
- https://www.vulncheck.com/advisories/bytestash-1.5.10-before-1.6.2-insufficient-session-expiration-via-api-keys (opens in a new tab)