# CVE-2026-105263: Shaarli Admin Metadata Endpoint MetadataController.php MetadataController server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the Shaarli admin metadata endpoint to access internal resources.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-105263, GHSA-2rmx-qf8h-6p5c, GHSA-85jx-fhrf-q9w7, UBUNTU-CVE-2026-105263

## What is CVE-2026-105263?

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

### Official description

A security flaw has been discovered in Shaarli up to 0.16.3. The affected element is the function MetadataController of the file application/front/controller/admin/MetadataController.php of the component Admin Metadata Endpoint. Performing a manipulation of the argument url results in server-side request forgery. The attack may be initiated remotely. Upgrading to version 0.16.4 is sufficient to fix this issue. The patch is named 8ca4de8e7c932a684481f5fbb1229fe16de1f4d2. It is advisable to upgrade the affected component.

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

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


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

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

## Is CVE-2026-105263 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105263 is a medium-severity server-side request forgery vulnerability in Shaarli, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105263 in the wild and no public exploit code.

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

## Sources

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

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