CVE-2026-110774
Deferred Deferred - Pending Action

Broken Access Control in Blinko Allows Unauthorized File Access

Vulnerability report for CVE-2026-110774, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-14

Last updated on: 2026-10-15

Assigner: VulnCheck

Description

Blinko through 1.8.8 contains a broken access control vulnerability in the /api/file route that allows authenticated users to read other users' private attachments due to a flawed owner check. Attackers can supply another user's stored filename, following a basename plus millisecond-timestamp pattern, to download private, non-shared attachments.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-14
Last Modified
2026-10-15
Generated
2026-10-19
AI Q&A
2026-10-15
EPSS Evaluated
2026-10-18
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
blinkospace blinko 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-110774 is a broken access control vulnerability in Blinko through version 1.8.8. It allows authenticated users to read private attachments belonging to other users via the /api/file route. The flaw stems from improper ownership verification, enabling attackers to access non-shared files by supplying a predictable filename format (basename plus millisecond-timestamp).

Detection Guidance

To detect this vulnerability, check if authenticated users can access private attachments via the /api/file route by requesting files with another user's filename pattern (basename plus millisecond-timestamp). Monitor logs for unauthorized file access attempts or unusual API calls to /api/file with non-owned filenames.

Impact Analysis

This vulnerability allows unauthorized users to access private files such as images or documents uploaded by others. While it does not permit write, update, or delete operations, it breaches cross-user confidentiality. Attackers with low privileges or API tokens can exploit it to view sensitive data.

Compliance Impact

This vulnerability could lead to non-compliance with data protection regulations like GDPR and HIPAA due to unauthorized access to private user data. It violates principles of data confidentiality and user consent, potentially resulting in legal and regulatory penalties.

Mitigation Strategies

Immediately update Blinko to the latest version beyond 1.8.8. Implement strict ownership verification in the /api/file route by replacing the flawed condition with an explicit check ensuring only the owner or authorized users can access files. Review logs for past unauthorized access and restrict API token permissions.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-110774. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart