dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2026-13341

HIGH · 7.4 CVSS v3.1 Published 2026-07-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges 7 weeks old

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 exists in the Kong Konnect Model Context Protocol (MCP) server prior to version 1.0.0, which could allow a remote attacker to perform an indirect prompt injection attack and execute unintended API requests.

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 confidence

The Kong Konnect MCP server before version 1.0.0 is vulnerable to indirect prompt injection, allowing remote attackers to craft malicious inputs that cause the AI to execute unintended API requests through the MCP server's tool-calling functionality.

MitigationUpgrade Kong Konnect MCP server to version 1.0.0 or later; if immediate upgrade is not feasible, implement input sanitization and validation for all data flowing into the MCP server from external sources.

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
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/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 checks

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

  1. Identify if Kong Konnect MCP server is installed
    Check for the presence of the Kong Konnect MCP server package or service in your environment. Look for processes named 'kong-konnect-mcp', 'konnect-mcp', or check installed packages using your package manager (npm list, pip list, or similar depending on installation method).
    Affected if The Kong Konnect MCP server is present in your environment
  2. Determine the installed version of Kong Konnect MCP server
    Run the version command for the MCP server (commonly: 'npx konnect-mcp --version', 'konnect-mcp --version', or check package.json/package-lock.json if installed as a Node package). Compare the version number to 1.0.0 using semantic version comparison.
    Affected if The installed version is earlier than 1.0.0 (e.g., 0.x.x, 0.9.x, etc.)
  3. Verify the MCP server's tool-calling functionality is enabled
    Examine the MCP server configuration file or environment variables. Look for settings that enable tool-calling, function execution, or API request capabilities (commonly in config files named 'config.json', 'config.yaml', '.env', or similar). Check for flags like 'enableTools', 'allowFunctionCalls', or similar boolean settings.
    Affected if Tool-calling functionality is enabled and accessible to the MCP server
  4. Check if the MCP server accepts external or untrusted inputs
    Review how data flows into the MCP server. Identify if external sources (user inputs, webhooks, third-party APIs, files from untrusted sources) can supply data to the MCP server without sanitization. Check for input endpoints, API interfaces, or integration points that accept external data.
    Affected if External or untrusted data can reach the MCP server without input validation

You are affected if the Kong Konnect MCP server is installed with a version earlier than 1.0.0 AND has tool-calling enabled with the ability to accept external inputs that could contain malicious prompt injection.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Kong Konnect MCP server to version 1.0.0 or later; if immediate upgrade is not feasible, implement input sanitization and validation for all data flowing into the MCP server from external sources.

Recommended fix Moderate confidence

Kong Konnect MCP server version 1.0.0 or later

  1. 1. Identify the current installed version of the Kong Konnect Model Context Protocol (MCP) server
  2. 2. If the current version is earlier than 1.0.0, upgrade to version 1.0.0 or later
  3. 3. Verify the upgrade was successful by checking the MCP server version
  4. 4. Test that legitimate MCP server functionality operates correctly after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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