CVE-2026-113597
Deferred Deferred - Pending Action

Insecure Direct Object Reference in Blinko via Tag tRPC Router

Publication date: 2026-10-20

Last updated on: 2026-10-20

Assigner: VulnCheck

Description
Blinko through 1.8.8 contains an insecure direct object reference vulnerability in the tag tRPC router that allows authenticated users to read and modify other users' tags by supplying arbitrary tag IDs. Attackers can enumerate sequential IDs via fullTagNameById, updateTagIcon, and updateTagOrder to reveal private note topics and tamper with tag icons and ordering.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-20
Last Modified
2026-10-20
Generated
2026-11-10
AI Q&A
2026-10-20
EPSS Evaluated
2026-11-08
NVD
CVE-2026-113597
EUVD
EUVD-2026-105163

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-113597 is an Insecure Direct Object Reference (IDOR) vulnerability in Blinko versions up to 1.8.8. It allows authenticated users to read or modify other users' tags by supplying arbitrary tag IDs. Attackers can enumerate sequential IDs via functions like fullTagNameById, updateTagIcon, and updateTagOrder to access private note topics and tamper with tag icons and ordering without proper authorization.

Detection Guidance

To detect this IDOR vulnerability in Blinko, monitor API calls to endpoints like fullTagNameById, updateTagIcon, and updateTagOrder. Check for requests with sequential tag IDs that return data not belonging to the authenticated user. Review logs for unauthorized modifications to tags or messages by non-owners.

Impact Analysis

This vulnerability allows attackers to access and modify other users' private data, including conversation history, tag names, icons, and ordering. It can lead to unauthorized data exposure, data tampering, and potential account compromise. The sequential ID enumeration makes exploitation straightforward for authenticated users.

Compliance Impact

This vulnerability likely violates compliance requirements for data protection and privacy regulations such as GDPR and HIPAA. It enables unauthorized access to and modification of user data, which could result in data breaches, loss of confidentiality, and failure to meet regulatory obligations for data integrity and access controls.

Mitigation Strategies

Upgrade Blinko to a version beyond 1.8.8 where ownership checks are enforced. Implement server-side validation to ensure users can only access or modify resources tied to their accountId. Review and patch the tag and message routers as shown in pull request #1171.

Chat Assistant

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

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...