# CVE-2026-13341: Prompt Injection and Credential Exposure via Untrusted Analytics Data in Kong Konnect MCP

> Remote attackers can perform indirect prompt injection to execute unintended API requests and expose credentials in Kong Konnect MCP.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-6pr5-9p6v-xxrq, GHSA-7767-3m3w-2p44

## What is CVE-2026-13341?

CVE-2026-13341 is a high-severity code injection vulnerability in KongHQ mcp-konnect, published on 3 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-13341?


## How do I fix CVE-2026-13341?

No fix has been published for CVE-2026-13341 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13341 being exploited?

There is no known exploitation of CVE-2026-13341 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13341 and fix it if it is affected.

What it is: CVE-2026-13341 is a high-severity code injection vulnerability in KongHQ mcp-konnect, published on 3 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-13341 in the wild and no public exploit code.

Affected product: KongHQ mcp-konnect. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-13341/ (Markdown: https://insights.sbomify.com/CVE-2026-13341/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13341
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13341
- OSV: https://osv.dev/vulnerability/CVE-2026-13341

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13341/
Summaries are generated and may contain mistakes; the official description above is the record.