# CVE-2026-110225: Shaarli through 0.16.9 SSRF via Thumbnail Retrieval update-thumbnail Route

> Authenticated users can exploit Shaarli's thumbnail retrieval to force server-side requests to internal or cloud metadata addresses, potentially exposing sensitive data.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-110225, GHSA-w44p-6p6v-f82x, UBUNTU-CVE-2026-110225

## What is CVE-2026-110225?

CVE-2026-110225 is a medium-severity server-side request forgery vulnerability in Shaarli, published on 13 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Shaarli through 0.16.9 contains a server-side request forgery vulnerability that allows authenticated users to make the server request internal addresses by fetching bookmark thumbnails without private-address checks. Attackers can create bookmarks pointing to loopback, private, or cloud metadata addresses and trigger ThumbnailsController::ajaxUpdate or saving to send blind GET requests, with open_shaarli exposing this to any visitor.

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

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


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

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

## Is CVE-2026-110225 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110225 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110225 is a medium-severity server-side request forgery vulnerability in Shaarli, published on 13 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-110225 exists.

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

## Sources

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

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