dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-7158

HIGH · 7.3 CVSS v3.1 Published 2026-04-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability has been found in dmitryglhf mcp-url-downloader up to 4b8cf2de55f6e8864a77d108e8a94a5b8e4394c6. Affected by this issue is the function _validate_url_safe of the file src/mcp_url_downloader/server.py. Such manipulation of the argument url leads to server-side request forgery. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The project was informed of the problem early through an issue report but has not responded yet.

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 · high confidence

Server-Side Request Forgery (SSRF) vulnerability in the _validate_url_safe function of src/mcp_url_downloader/server.py. The function fails to properly validate or restrict URL inputs, allowing remote attackers to manipulate the url parameter to cause the server to make requests to arbitrary internal or external resources.

MitigationImplement strict URL validation in _validate_url_safe: restrict allowed URL schemes to http/https only, implement an explicit allowlist of permitted hostnames/IPs, and add network-level restrictions to prevent access to internal services (localhost, private IPs, cloud metadata endpoints).

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if mcp_url_downloader is installed
    Run 'pip show mcp_url_downloader' or check your project's dependencies (requirements.txt, pyproject.toml, Pipfile) for the mcp_url_downloader package and note its installed version
    Affected if The package is installed and its version falls within any affected range or is a version where the vulnerability is present
  2. Locate the vulnerable server.py file
    Find the file at src/mcp_url_downloader/server.py in your environment (check your site-packages, venv, or project source directory)
    Affected if The file exists in your environment, indicating the vulnerable code is present
  3. Inspect the _validate_url_safe function implementation
    Open src/mcp_url_downloader/server.py and locate the _validate_url_safe function; examine its URL validation logic for any allowed schemes (http/https), hostname allowlists, or IP range restrictions
    Affected if The function exists but lacks proper validation (no scheme restrictions, no hostname allowlist, no blocking of localhost/private IPs)
  4. Determine if URL download functionality is enabled
    Check your application configuration, startup logs, or active endpoints to see if the URL downloader server feature is running or exposed
    Affected if The URL downloader server is actively running and accessible (even locally)
  5. Test for SSRF exposure
    If the service is running, attempt to send a request with a url parameter pointing to an internal resource (e.g., http://localhost:port/path or http://169.254.169.254/) and observe if the server attempts the connection
    Affected if The server accepts and attempts to follow arbitrary URLs, including internal addresses

Your environment is affected if mcp_url_downloader is installed, the vulnerable server.py with _validate_url_safe is present, and the URL downloader functionality is enabled without proper URL validation safeguards in place.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict URL validation in _validate_url_safe: restrict allowed URL schemes to http/https only, implement an explicit allowlist of permitted hostnames/IPs, and add network-level restrictions to prevent access to internal services (localhost, private IPs, cloud metadata endpoints).

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7158 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7158 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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