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

CVE-2026-14748

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-05

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

69/100

Remediation priority · Elevated

Remotely reachable Zero-click 6 weeks old

Official description

NVD · unedited

A flaw has been found in AIAnytime Awesome-MCP-Server up to a884bb51bcd99e08e14fd712c749d55d9d9a13ab. Affected by this issue is some unknown functionality of the file mcp-wiki/src/mcp_wiki/server.py of the component mcp-wiki/wiki-summary. This manipulation of the argument url causes server-side request forgery. The attack may be initiated remotely. The exploit has been published and may be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The project was informed of the problem early through an issue report but has not responded yet.

Technical summary

dbcve analysis · moderate confidence

Server-side request forgery (SSRF) vulnerability in the mcp-wiki/wiki-summary component of Awesome-MCP-Server allows remote attackers to make the server perform arbitrary requests by manipulating the url parameter. The vulnerable code in mcp-wiki/src/mcp_wiki/server.py does not validate or restrict the URL input before making HTTP requests.

MitigationImplement strict URL validation using an allowlist approach to restrict URLs to trusted domains/patterns, or disable the wiki-summary functionality until a fix is available from the vendor.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

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

Am I affected?

dbcve checks

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

Identify if Awesome-MCP-Server is installed

Check for the presence of the Awesome-MCP-Server package or repository in your environment. Look for a directory named 'Awesome-MCP-Server' or check your Python packages with 'pip list | grep -i mcp' or equivalent.

Affected if The Awesome-MCP-Server package is present in your environment
Locate the mcp-wiki component

Navigate to the mcp-wiki directory within Awesome-MCP-Server, specifically look for mcp-wiki/src/mcp_wiki/server.py

Affected if The file mcp-wiki/src/mcp_wiki/server.py exists in your installation
Verify the wiki-summary functionality is exposed

Check your MCP server configuration or startup files to determine if the wiki-summary tool/feature is enabled and accessible to clients. Look for wiki-summary in your tool registration or exposed endpoints.

Affected if The wiki-summary component is registered as an available tool or exposed via API
Inspect the server.py code for URL handling

Open mcp-wiki/src/mcp_wiki/server.py and search for the wiki-summary handler function. Examine how the 'url' parameter is processed - look for lack of URL validation before HTTP requests are made.

Affected if The code passes the url parameter directly to an HTTP request without validation or allowlist checking
Compare installed version to known affected code

Check your installed version of Awesome-MCP-Server by reviewing git tags, package version, or the server.py modification date. Since no specific version range is provided, assume versions containing the vulnerable code pattern are affected.

Affected if Your version contains the code in mcp-wiki/src/mcp_wiki/server.py that makes HTTP requests without validating the url parameter

You are affected if Awesome-MCP-Server with the mcp-wiki component is installed and the wiki-summary functionality is enabled, with the vulnerable code present in server.py making unchecked HTTP requests.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Implement strict URL validation using an allowlist approach to restrict URLs to trusted domains/patterns, or disable the wiki-summary functionality until a fix is available from the vendor.

Have this fixed Scoped from the published advisory

Consultation4.0 h
Implementation4.0 h
Testing4.0 h
Review / QA4.0 h

16.0 hours of engineering $2,840

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-14748 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-14748?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 6.3 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

Need this fixed?

Have this fixed 16 hrs · Moderate

Typical engagement from $2,840

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-14748 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References