# CVE-2026-92760: Shlink through 5.1.6 Mercure Token Authorization Bypass

> Attackers with restricted API keys can bypass authorization to access sensitive visit data for URLs outside their permitted scope.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA: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:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-r72g-8wq6-6m7w

## What is CVE-2026-92760?

CVE-2026-92760 is a high-severity missing authorization vulnerability in shlinkio shlink, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Shlink through 5.1.6 fails to enforce API key role restrictions when issuing Mercure subscription tokens, allowing restricted keys to subscribe to all topics. Attackers with author-only or domain-only keys can access the mercure-info endpoint to receive visit data including referrer, user agent, geolocation, and full short URL objects for URLs outside their authorization boundary.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-92760 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92760 is a high-severity missing authorization vulnerability in shlinkio shlink, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92760 exists.

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

## Sources

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

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