Blinko is an AI-powered card note-taking project. Prior to version 1.8.4, a publicly accessible endpoint exposes all user information, including usernames, roles, and account creation dates. This issue has been patched in version 1.8.4.
CVE-2026-23486
MEDIUMNVD 5.36.9Trending — 3 sources updated this weekElevated
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 6.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: cna:github_m
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.3Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 6.9(low)
- EG Risk
- 46(Track)EG Risk 46/100SSVC: Track
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 computedSeverity69% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 50%
- KEV
- Not listed
Published
March 23, 2026
Last Modified
June 17, 2026
References (3)
- security-advisories@githubhttps://github.com/blinkospace/blinko/commit/ec1e3e20384b620b8bf928fe80b4d8546757b419
- security-advisories@githubhttps://github.com/blinkospace/blinko/releases/tag/1.8.4
- security-advisories@githubhttps://github.com/blinkospace/blinko/security/advisories/GHSA-446p-2xf5-frxf
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 12:50 UTCEG score recompute
- 2026-07-27 12:50 UTCOSV refresh
Publicly available exploits
(1 reference)Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Nucleihttp/cves/2026/CVE-2026-23486.yamlFirst seen Jan 1, 2026
Blinko <= 1.8.3 - User Information Leak
Open source ↗
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-23486?
CVE-2026-23486 is a medium vulnerability published on March 23, 2026. Blinko is an AI-powered card note-taking project. Prior to version 1.8.4, a publicly accessible endpoint exposes all user information, including usernames, roles, and account creation dates. This issue has been patched in version 1.8.4.
When was CVE-2026-23486 disclosed?
CVE-2026-23486 was first published in the National Vulnerability Database on March 23, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23486 actively exploited?
CVE-2026-23486 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 50.0% of all scored CVEs.
What is the CVSS score of CVE-2026-23486?
CVE-2026-23486 has a CVSS v3 base score of 5.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 6.9. The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-23486?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23486, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-23486
Is Your Infrastructure Affected by CVE-2026-23486?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.