Skip to main content
VulnerabilityPublished

CVE-2026-23482: blinkospace blinko · Path Traversal

Affects blinkospace blinkoSource CVE Database V5

0
Compare

Not known to be exploited · public detection template (Nuclei) · CVSS 8.2 High : upgrade to 1.8.4 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.5% chance of exploitation in 30 days – higher than 74% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.8.4
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Mar 2026

  2. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade blinko and blinkospace/blinko to 1.8.4.

Affected software

ProductAffectedFixed in
blinkospaceblinkoAffected
  • <1.8.4
Fixed in
  • 1.8.4
GitHubblinkospace/blinkopkg:github/blinkospace/blinkoOther threatsAffected
  • <1.8.4
Fixed in
  • 1.8.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade Blinko to version 1.8.4 or later, where this vulnerability is patched. If upgrading is not immediately possible, implement strict network-level access controls to restrict access to the Blinko file server endpoint, especially the temp/ directory. Disable scheduled backup tasks temporarily until the patch is applied to prevent exposure of backup files. Conduct thorough audits of server file permissions and ensure that file-serving endpoints validate and sanitize all user inputs to prevent path traversal sequences. Employ web application firewalls (WAFs) with custom rules to detect and block path traversal attempts targeting the temp/ directory. Monitor logs for suspicious access patterns indicative of path traversal exploitation attempts. Educate developers on secure coding practices related to file handling and input validation to prevent similar vulnerabilities in future releases.

Description

Blinko is an AI-powered card note-taking project. Prior to version 1.8.4, the file server endpoint does not perform permission checks on the temp/ path and does not filter path traversal sequences, allowing unauthorized attackers to read arbitrary files on the server. When scheduled backup tasks are enabled, attackers can read backup files to obtain all user notes and user TOKENS. This issue has been patched in version 1.8.4.

References

Community reviews

Loading reviews…