CVE-2026-50887
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in shlink v5.0.1's automatic short URL title resolution feature. Attackers can supply a crafted longUrl parameter to make the server perform requests to internal resources, enabling port scanning and access to internal services that should not be exposed.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm shlink installation and versionRun 'shlink --version' or check your package manager for installed shlink version. Compare the version number to 5.0.1 specifically.Affected if The installed version is exactly 5.0.1 or falls within the 5.0.x range where the vulnerability exists.
-
Locate the title resolution feature configurationExamine shlink's configuration files (typically in /etc/shlink, configmap, or environment variables) for settings related to URL title fetching or metadata retrieval from URLs.Affected if The automatic URL title resolution feature is present and configurable in your shlink deployment.
-
Verify if automatic title resolution is enabledCheck configuration for settings like 'TITLE_RESOLUTION_ENABLED', 'FETCH_OPEN_TAGS', or similar options that control whether shlink automatically fetches titles from user-provided URLs.Affected if Automatic title resolution is turned ON and processes URLs submitted by users through the API or UI.
-
Identify if longUrl parameter is acceptedReview API endpoints that accept URL creation requests (typically POST /short-urls or similar). Look for parameters named 'longUrl', 'url', or similar that accept arbitrary URLs for shortening.Affected if Users can submit arbitrary long URLs through the API and the system attempts to resolve titles from those URLs.
You are affected if shlink version 5.0.1 is running and the automatic title resolution feature is enabled, allowing user-supplied URLs to trigger server-side requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict URL validation in the title resolution component to reject URLs targeting internal/private IP addresses (127.0.0.1, 10.x.x.x, 192.168.x.x, etc.), localhost, and internal hostnames. Consider implementing an allowlist of permitted domains or disabling automatic title resolution for user-supplied URLs.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-50887 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-50887 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data