Skip to main content

Blinko CVE-2026-23485

| EUVDEUVD-2026-14539 MEDIUM
Path Traversal (CWE-22)
2026-03-23 GitHub_M
5.3
CVSS 3.1 · GitHub Advisory
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

While the CVSS 6.9 score reflects the network-accessible nature and lack of privilege requirements (AV:N, PR:N, UI:N), the actual real-world risk is moderate. The CVSS vector indicates low confidentiality impact (VC:L) with no integrity, availability, or scope changes—confirming this is an information disclosure issue, not a critical system compromise. The vulnerability is automatable and requires no user interaction, which elevates exploitation probability; however, the impact is limited to file enumeration rather than full file read or command execution. The existence of a public advisory, confirmed patch commit (9d6fa80a3e11a99886f90e048657443335fd3e7d), and released patch (version 1.8.4) indicate responsible disclosure. This is a legitimate security issue that warrants patching, but it does not constitute a zero-day or critical infrastructure threat—it is a typical path traversal reconnaissance vector suitable for standard security hygiene practices.

Exploit ScenarioDerived

An unauthenticated attacker probes the Blinko application by submitting HTTP requests with payloads such as 'filePath=../../../../etc/passwd' and observes the server's error responses. By comparing response codes and error messages (e.g., 'file not found' versus 'access denied'), the attacker maps the server's file system structure and identifies the existence of sensitive files such as configuration files, private keys, or database files. This information enables downstream attacks such as social engineering, targeted exploitation of known services, or identification of other vulnerabilities. The low attack complexity (AC:L) and network accessibility mean this can be executed rapidly with automated scanning tools.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 23, 2026

Blinko, an AI-powered card note-taking application, contains a path traversal vulnerability in the filePath parameter that allows unauthenticated remote attackers to enumerate file existence on the server through differential error responses. Versions prior to 1.8.4 are affected, and an attacker can leverage this vulnerability to discover sensitive files and directories without authentication or user interaction. The vulnerability has been patched in version 1.8.4, and exploit code or proof-of-concept demonstrations are available via the GitHub security advisory.

RemediationAI

Upgrade Blinko to version 1.8.4 or later immediately by downloading the patched release from https://github.com/blinkospace/blinko/releases/tag/1.8.4. The fix is available in commit 9d6fa80a3e11a99886f90e048657443335fd3e7d and has been verified through the official GitHub Security Advisory at https://github.com/blinkospace/blinko/security/advisories/GHSA-5x64-pmfq-pw7q. If immediate patching is not feasible, restrict network access to the Blinko service via firewall rules or reverse proxy configuration, limit exposure to trusted internal networks only, and disable public internet access until patching is completed. Monitor application logs for suspicious filePath parameter usage patterns that may indicate reconnaissance attempts.

Affected VersionsENISA

blinko < 1.8.4

Affected Packages

euvd blinko fix: 1.8.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability stems from improper input validation of the filePath parameter, which fails to sanitize path traversal sequences such as '../' before processing file operations. This is classified as CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) and represents a common weakness in web applications that accept user-supplied file paths without adequate canonicalization or validation. Blinko (cpe:2.3:a:blinkospace:blinko:*:*:*:*:*:*:*:*) implements file-based operations as part of its note-taking functionality, and the application fails to restrict access to files within intended directories. The error response differentiation (such as 'file not found' versus 'permission denied' versus 'access error') allows attackers to infer file system structure without actually reading file contents, making this a reconnaissance vulnerability with high confidence in enumeration results.

Know when Blinko gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

GitHub Advisory PRIMARY 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

2
Patch available
Apr 16, 2026 - 05:29 EUVD
1.8.4
CVE Published
Mar 23, 2026 - 20:50 nvd
MEDIUM 5.3

DescriptionGitHub Advisory

Blinko is an AI-powered card note-taking project. Prior to version 1.8.4, the filePath parameter accepts path traversal sequences, allowing enumeration of file existence on the server via different error responses. This issue has been patched in version 1.8.4.

Executive ViewAI

Why It Matters

Organizations using Blinko should be aware of moderate risk from CVE-2026-23485, a path traversal vulnerability rated CVSS 5.3. This could allow unauthorized file access. Organizations should apply vendor updates when available and monitor for exploitation.

Business Impact: Low
Compensating Controls

Apply vendor patch. If patching is delayed: restrict file access via WAF, implement allowlists.

Threat Intelligence Overview

EPSS Score
0.1%
Top 82% exploitable
Data Quality
5 sources
Confidence: Medium
EUVD NVD CVE.org EPSS Vulnrichment GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.1%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Low
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

More in Blinko

View all
CVE-2026-23482 HIGH POC
7.5 Mar 23

Blinko, an AI-powered card note-taking application, contains a path traversal vulnerability in its file server endpoint

CVE-2026-23486 MEDIUM POC
5.3 Mar 23

A publicly accessible endpoint in Blinko prior to version 1.8.4 discloses sensitive user information including usernames

CVE-2026-23483 MEDIUM POC
5.3 Mar 23

Blinko versions 1.8.3 and earlier contain a path traversal vulnerability in the plugin file server endpoint that fails t

CVE-2026-23480 HIGH
8.8 Mar 23

Blinko versions prior to 1.8.4 contain a critical privilege escalation vulnerability in the upsertUser endpoint that all

CVE-2026-85607 HIGH
8.7 Sep 04

Insecure Direct Object Reference (IDOR) in Blinko 1.8.7 allows any authenticated user to read, modify, and delete AI cha

CVE-2026-23882 HIGH
7.2 Mar 23

Blinko versions prior to 1.8.4 allow authenticated high-privilege users to execute arbitrary commands through the MCP se

CVE-2026-85624 HIGH
7.1 Sep 04

Cross-user private note disclosure in Blinko 1.8.7 allows any authenticated user to read other users' private notes, att

CVE-2026-23487 MEDIUM
6.5 Mar 23

An Insecure Direct Object Reference (IDOR) vulnerability in Blinko versions prior to 1.8.4 allows authenticated attacker

CVE-2026-23484 MEDIUM
6.5 Mar 23

Blinko versions 1.8.3 and earlier allow authenticated users to write arbitrary files to the filesystem through an unvali

CVE-2026-23481 MEDIUM
6.5 Mar 23

Blinko, an AI-powered card note-taking application, contains an authenticated arbitrary file write vulnerability in the

CVE-2026-23488 MEDIUM
5.3 Mar 23

Blinko, an AI-powered card note-taking application, contains an authentication bypass vulnerability in its comment manag

CVE-2026-113597 MEDIUM
5.3 Oct 20

An insecure direct object reference (CWE-639) in Blinko through 1.8.8 lets any authenticated user read and modify tags b

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy