# CVE-2026-50887: shlink has a Server-Side Request Forgery issue

> Attackers can scan internal resources by supplying a crafted longUrl to the automatic short URL title resolution component.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-p85r-x2wj-mxqj

## What is CVE-2026-50887?

CVE-2026-50887 is a critical server-side request forgery vulnerability in n/a, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Server-Side Request Forgery (SSRF) in the automatic short URL title resolution component of shlink v5.0.1 allows attackers to scan internal resources via supplying a crafted longUrl.

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

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

2 open source packages ship an affected version, including shlinkio/shlink.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `shlinkio/shlink` | Packagist | All versions to 5.0.1 | None |
| `shlinkio/shlink` | Packagist | All versions to 5.0.1 | None |

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

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

## Is CVE-2026-50887 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50887 is a critical server-side request forgery vulnerability in n/a, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50887 exists.

Affected packages and fixed versions:
- shlinkio/shlink (Packagist): affected all versions up to 5.0.1; no fix listed
- shlinkio/shlink (Packagist): affected all versions up to 5.0.1; no fix listed

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

## Sources

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

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