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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 2
- StatusReceived → DeferredNVD modified 2026-10-15 14:47
- First seenCVSS 6.0NVD modified 2026-10-14 19:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 4
- https://github.com/blinkospace/blinko
- https://github.com/blinkospace/blinko/blob/178e4b3538a21823a50ac2481e653d56cb1ffa86/server/routerExpress/file/file.ts#L148
- https://hackmd.io/@hieuPenguinnn/blinko-attachment-accountid-idor
- https://www.vulncheck.com/advisories/blinko-through-1.8.8-private-attachment-read-via-api-file-route