# CVE-2026-72591: Koito - Authenticated Server-Side Request Forgery via Album Image URL Parameter

> Authenticated attackers can force the Koito server to make arbitrary HTTP requests via the album image URL parameter, potentially accessing internal resources.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-hwrh-8qfp-c4p6

## What is CVE-2026-72591?

CVE-2026-72591 is a high-severity server-side request forgery vulnerability in gabehf Koito, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A server-side request forgery (SSRF) vulnerability in gabehf/Koito through v0.3.2 allows an authenticated user to make the server perform HTTP requests to arbitrary internal or external hosts by supplying a crafted image_url value in the PATCH /apis/web/v1/album/{id}/image endpoint.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-72591 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72591 is a high-severity server-side request forgery vulnerability in gabehf Koito, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72591 in the wild and no public exploit code.

Affected product: gabehf Koito. 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-72591/ (Markdown: https://insights.sbomify.com/CVE-2026-72591/index.md)
```

## Sources

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

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