# CVE-2026-85605: Slink before 1.12.3 Missing Authorization on Image Comment Endpoints

> Unauthenticated attackers can read image comment threads and subscribe to live updates without authorization checks.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-9hc4-c397-v2vf, GHSA-hxx4-4hwq-8258

## What is CVE-2026-85605?

CVE-2026-85605 is a medium-severity missing authorization vulnerability in andrii-kryvoviaz slink, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Slink before 1.12.3 fails to properly authorize access to image comment endpoints, allowing unauthenticated attackers to read comment threads via GET /api/image/{imageId}/comments and server-sent-events subscriptions. Attackers who obtain image IDs out of band can retrieve full comment threads on public images and subscribe to live comment updates without authentication or authorization checks.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-85605?


## How do I fix CVE-2026-85605?

No fix has been published for CVE-2026-85605 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85605 being exploited?

There is no known exploitation of CVE-2026-85605 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85605 and fix it if it is affected.

What it is: CVE-2026-85605 is a medium-severity missing authorization vulnerability in andrii-kryvoviaz slink, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-85605 in the wild and no public exploit code.

Affected product: andrii-kryvoviaz slink. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85605/ (Markdown: https://insights.sbomify.com/CVE-2026-85605/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85605
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85605
- OSV: https://osv.dev/vulnerability/CVE-2026-85605

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85605/
Summaries are generated and may contain mistakes; the official description above is the record.