Is CVE-2026-50887 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-50887 being exploited in the wild.

How severe is CVE-2026-50887?

Critical severity, with a CVSS score of 9.1, published 15 June 2026.

Which products and versions are affected?

shlinkio/shlink (Packagist) <= 5.0.1, ECOSYSTEM:introduced=0,last_affected=5.0.1; Shlink 5.0.1.

Is there a fix for CVE-2026-50887?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-50887 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-50887?

Check whether you run shlinkio/shlink (Packagist) or Shlink at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-50887: Shlink SSRF in automatic short URL title resolution

Q: Is there a fix for CVE-2026-50887?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

Q: How is CVE-2026-50887 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-50887?

Check whether you run shlinkio/shlink (Packagist) or Shlink at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-50887 · Severity: critical · CVSS 9.1 · Published 2026-06-15

Shlink is a URL shortening service that can automatically resolve and display page titles from long URLs. A vulnerability in this feature allows authenticated users with an API key to make the Shlink server perform HTTP requests to internal network resources and leak the titles of those pages back to the attacker. This could expose sensitive internal systems and services that should not be accessible from the internet.

Technologies: Shlink. Vendors: Packagist, Shlink.

Quick answers

Is CVE-2026-50887 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50887 being exploited in the wild.
How severe is CVE-2026-50887?: Critical severity, with a CVSS score of 9.1, published 15 June 2026.
Which products and versions are affected?: shlinkio/shlink (Packagist) <= 5.0.1, ECOSYSTEM:introduced=0,last_affected=5.0.1; Shlink 5.0.1.
Is there a fix for CVE-2026-50887?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-50887 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-50887?: Check whether you run shlinkio/shlink (Packagist) or Shlink at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a Server-Side Request Forgery (SSRF) in the automatic title-resolution helper used during short URL creation and editing. When AUTO_RESOLVE_TITLES is enabled and no explicit title is supplied, the application performs a server-side GET request to the user-controlled longUrl parameter without validating that it points to an external, safe destination. The vulnerable component accepts URL-shaped values and does not enforce internal-address blocking before fetching the URL. An authenticated attacker with a valid API key can trigger requests to internal HTTP services; the fetched page title is then stored or returned with the short URL, providing a response-content disclosure primitive. Attack preconditions include the AUTO_RESOLVE_TITLES feature being enabled and the attacker possessing a valid API key. No patch has been released as of the advisory publication date.

Affected products

shlinkio shlink <= 5.0.1

Identifiers

CVE-2026-50887
GHSA-p85r-x2wj-mxqj

Timeline

2026-06-15: disclosed: Vulnerability published to GitHub Advisory Database and NVD
2026-08-27: advisory: GitHub security review completed

References

https://gist.github.com/pyuysig/9de95fb39eb089a4346570d791af99a6

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.