# CVE-2026-126658: ByteStash 1.5.10 before 1.6.2 Insufficient Session Expiration via API Keys

> Holders of deactivated ByteStash API keys keep reading, creating, modifying and deleting snippets and MCP tool access.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-26m9-ww2j-3cr5, GHSA-45rq-x49h-cmwp

## What is CVE-2026-126658?

CVE-2026-126658 is a medium-severity authentication bypass vulnerability in jordan-dalby ByteStash, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2026-126658?

An affected version is exposed as installed. No special setting or call is needed.


## How do I fix CVE-2026-126658?

No fix has been published for CVE-2026-126658 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126658 being exploited?

There is no known exploitation of CVE-2026-126658 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126658 and fix it if it is affected.

What it is: CVE-2026-126658 is a medium-severity authentication bypass vulnerability in jordan-dalby ByteStash, published on 11 Nov 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126658 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: jordan-dalby ByteStash. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126658/ (Markdown: https://insights.sbomify.com/CVE-2026-126658/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126658
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126658
- OSV: https://osv.dev/vulnerability/CVE-2026-126658

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126658/
Summaries are generated and may contain mistakes; the official description above is the record.
