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.
CVE-2026-126658
MEDIUMPre-NVD 5.45.4ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 5.4 from GitHub Security Advisory (severity: MODERATE) published 2026-11-11. A secondary CVSS source baseline 5.4; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-123402 (ENISA EUVD) · GHSA-45rq-x49h-cmwp (GitHub Security Advisories)Source: ENISA EUVD
5.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.4Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 5.4
- EG Score
- 5.4MEDIUMhigh confidence
- EG Risk
- 40EG Risk 40/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity54% × 45%Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.2%
- EPSS %ILE
- 14th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-13). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 11, 2026
Last Modified
November 13, 2026
Advisory Details (5)
Auto-updated Nov 13, 2026🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
Web page
ByteStash 1.5.10 before 1.6.2 Insufficient Session Expiration via API Keys | Advisories | VulnCheck
https://www.vulncheck.com/advisories/bytestash-1.5.10-before-1.6.2-insufficient-session-expiration-via-api-keysWeb page
ByteStash/server/src/repositories/apiKeyRepository.js at v1.6.1 · jordan-dalby/ByteStash · GitHub
https://github.com/jordan-dalby/ByteStash/blob/v1.6.1/server/src/repositories/apiKeyRepository.js#L70-L78GitHub release Patch Available
ByteStash v1.6.2
Patch available: jordan-dalby/ByteStash v1.6.2
https://github.com/jordan-dalby/ByteStash/releases/tag/v1.6.2GitHub commit Patch Available
commit eb4ecdfc30f2 (jordan-dalby/ByteStash)
Patch available: jordan-dalby/ByteStash v1.6.2 (contains commit eb4ecdfc30f2)
https://github.com/jordan-dalby/ByteStash/commit/eb4ecdfc30f2e7d1424137fa7fe3a9eed663218bGitHub advisoryMentions a patch (unverified)🟡 PoC Available
API keys of deactivated users remain valid on all /api/snippets* and /mcp endpoints · Advisory · jordan-dalby/ByteStash · GitHub
https://github.com/jordan-dalby/ByteStash/security/advisories/GHSA-26m9-ww2j-3cr5Vendor Advisories for CVE-2026-126658(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 9× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-13 18:34 UTCEchelonGraph re-scored
- 2026-11-13 18:34 UTCGHSA enrichmentGHSA-45rq-x49h-cmwp · GitHub severity MODERATE · GitHub CVSS 5.4
- 2026-11-13 17:49 UTCEchelonGraph re-scored
- 2026-11-13 17:49 UTCGHSA enrichmentGHSA-45rq-x49h-cmwp · GitHub severity MODERATE · GitHub CVSS 5.4
- 2026-11-13 17:18 UTCEchelonGraph re-scored
- 2026-11-13 17:18 UTCGHSA enrichmentGHSA-45rq-x49h-cmwp · GitHub severity MODERATE · GitHub CVSS 5.4
- 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-11-12 21:50 UTCEchelonGraph re-scored
- 2026-11-12 21:50 UTCGHSA enrichmentGHSA-45rq-x49h-cmwp · GitHub severity MODERATE · GitHub CVSS 5.4
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
- 2026-11-11 15:47 UTCEchelonGraph re-scored
- 2026-11-11 15:47 UTCGHSA enrichmentGHSA-45rq-x49h-cmwp · GitHub severity MODERATE · GitHub CVSS 5.4
- 2026-11-11 13:28 UTCEchelonGraph re-scored
- 2026-11-11 13:00 UTCENISA EUVD ID recordedEUVD-2026-123402 · Source: ENISA EUVD
- 2026-11-11 12:34 UTCEchelonGraph re-scoredFirst assessed: 5.4 MEDIUM
- 2026-11-11 12:33 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-126658?
CVE-2026-126658 is a medium-severity vulnerability; its CVE record was published on November 11, 2026. 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…
When was CVE-2026-126658 made public?
CVE-2026-126658 was made public on November 10, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 11, 2026. EchelonGraph's copy of the record carries a last-modified date of November 13, 2026; the record at its source may have been updated since.
Is CVE-2026-126658 actively exploited?
CVE-2026-126658 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-126658?
CVE-2026-126658 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-126658?
A fix for CVE-2026-126658 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-126658 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-126658
Is Your Infrastructure Affected by CVE-2026-126658?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.