A vulnerability has been found in BlackBeltTechnology pi-agent-dashboard up to 0.8.0. Affected by this issue is the function terminalManager.spawn of the file packages/server/src/browser-handlers/terminal-handler.ts of the component Terminal Handler. The manipulation of the argument cwd leads to improper authorization. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier of the patch is 48fd0bad5adfe76af9736599699d51a5f60019f6. It is suggested to install a patch to address this issue. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.
CVE-2026-108890
“—” beside the score: it is equal to the CVSS score beside it.
Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-10-12. The CNA's CVSS baseline 6.3; sources differ by 0.0.
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.
- CVSS v3
- 6.3
- EG Score
- 6.3MEDIUMhigh confidence
- EG Risk
- 28EG Risk 28/100
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computed (value × EchelonGraph’s weight)Severity63% × 45%The EG Score, 6.3 of 10.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.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: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
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.
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
October 12, 2026
Last Modified
October 13, 2026
Advisory Details (5)
Auto-updated Oct 12, 2026GitHub - BlackBeltTechnology/pi-agent-dashboard: Real-time web dashboard for pi coding-agent sessions. Multi-session view, live chat mirroring, integrated terminal, diff viewer, pi-flows execution, and mobile-first remote control via mDNS or zrok tunnel. Coexists with pi's TUI — doesn't replace it. · GitHub
https://github.com/BlackBeltTechnology/pi-agent-dashboard/commit 48fd0bad5adf (BlackBeltTechnology/pi-agent-dashboard)
Fix landed in BlackBeltTechnology/pi-agent-dashboard commit 48fd0bad5adf — awaiting tagged release
https://github.com/BlackBeltTechnology/pi-agent-dashboard/commit/48fd0bad5adfe76af9736599699d51a5f60019f6pi-agent-dashboard-RCE - Google Drive
https://drive.google.com/drive/folders/1obmr5PquMxcl6fMe2HohWDPQCg5uLDBB?usp=drive_linkfix(fix-ws-origin-cswsh): gate cross-site WebSocket and mutating REST by Origin (#625)
Fix merged in BlackBeltTechnology/pi-agent-dashboard PR #636 on 2026-09-12 — awaiting tagged release
https://github.com/BlackBeltTechnology/pi-agent-dashboard/pull/636Unauthenticated Cross-Site WebSocket Hijacking (CSWSH) in the local dashboard server leads to Remote Code Execution · Issue #625 · BlackBeltTechnology/pi-agent-dashboard · GitHub
https://github.com/BlackBeltTechnology/pi-agent-dashboard/issues/625Vendor Advisories for CVE-2026-108890(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 11× 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 it from the CNA feed. 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). Most recent first.
- 2026-10-13 15:22 UTCEG score recompute
- 2026-10-13 15:22 UTCGHSA enrichmentGHSA-q84p-gr6q-mp6g · GitHub severity LOW · GitHub CVSS 6.3
- 2026-10-13 15:19 UTCMITRE cvelistV5CVSS v4 → 5.3
- 2026-10-13 13:53 UTCEG score recompute
- 2026-10-13 13:52 UTCGHSA enrichmentGHSA-q84p-gr6q-mp6g · GitHub severity LOW · GitHub CVSS 6.3
- 2026-10-12 16:38 UTCEG score recompute
- 2026-10-12 14:44 UTCNVD updateCVSS v4 → 2.1
- 2026-10-12 14:26 UTCEG score recompute
- 2026-10-12 14:24 UTCNVD updateCVSS v4 → 2.1
- 2026-10-12 13:54 UTCEG score recomputeFirst assessed: 6.3 MEDIUM
- 2026-10-12 13:51 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-108890?
When was the CVE record for CVE-2026-108890 published?
What is the CVSS score of CVE-2026-108890?
How do I remediate CVE-2026-108890?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-108890
Is Your Infrastructure Affected by CVE-2026-108890?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.