CVE-2026-85607
Received Received - Intake

Authorization Bypass via IDOR in Blinko 1.8.7

Publication date: 2026-09-04

Last updated on: 2026-09-04

Assigner: VulnCheck

Description
Blinko 1.8.7 contains an authorization bypass (IDOR) vulnerability in multiple tRPC procedures (message.list, message.update, message.delete, message.clearAfter in server/routerTrpc/message.ts and conversation.clearMessages in server/routerTrpc/conversation.ts). Although these procedures require authentication, they query the database by caller-supplied conversation or message ID without verifying that the resource belongs to the requesting account. Any authenticated user can therefore read another user's full AI chat history, modify individual message content, and delete or wipe entire conversations by enumerating sequential integer IDs.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-04
Last Modified
2026-09-04
Generated
2026-09-04
AI Q&A
2026-09-04
EPSS Evaluated
N/A
NVD
CVE-2026-85607
EUVD
EUVD-2026-71223

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
blinkospace blinko to 1.8.8 (inc)
blinko blinko 1.8.7

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-85607 is an Insecure Direct Object Reference (IDOR) vulnerability in Blinko 1.8.7. It allows authenticated users to bypass authorization checks in multiple tRPC procedures (message.list, message.update, message.delete, message.clearAfter, conversation.clearMessages). These procedures query the database using user-supplied IDs without verifying ownership, enabling access to other users' AI chat histories, message modifications, and conversation deletions by enumerating sequential IDs.

The flaw exists because the application fails to enforce proper access controls despite requiring authentication. This compromises confidentiality, integrity, and availability of user data.

Detection Guidance

To detect this IDOR vulnerability in Blinko, monitor tRPC API calls for message.list, message.update, message.delete, message.clearAfter, and conversation.clearMessages. Check for requests with sequential integer IDs not matching the authenticated user's data. Use tools like Burp Suite or OWASP ZAP to intercept and analyze API traffic for unauthorized access patterns.

Impact Analysis

If you use Blinko 1.8.7, an attacker could access your private AI chat history, modify your messages, or delete entire conversations. Since IDs are sequential, attackers can easily guess and access other users' data. This could lead to privacy breaches, misinformation, or data loss.

Compliance Impact

This vulnerability likely violates GDPR's data protection principles (Article 5) and HIPAA's integrity and confidentiality requirements. It enables unauthorized access to personal data, compromising compliance with privacy regulations that mandate strict access controls and data protection measures.

Mitigation Strategies

Immediately upgrade Blinko to the latest patched version. Implement strict ownership validation for all tRPC procedures by verifying conversation/message IDs belong to the requesting user. Add rate limiting to prevent ID enumeration. Review database logs for suspicious activity involving sequential ID access.

Chat Assistant

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

EPSS Chart