Is CVE-2026-13341 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-13341 being exploited in the wild.

How severe is CVE-2026-13341?

High severity, with a CVSS score of 7.4, published 3 July 2026.

Is there a fix for CVE-2026-13341?

A patch was published on 2026-07-03: Version 1.0.0 released with fixes Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-13341 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-13341?

Check whether you run Kong Mcp-Konnect at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-13341: Kong Konnect MCP prompt injection and credential exposure

CVE-2026-13341 · Severity: high · CVSS 7.4 · Published 2026-07-03

A vulnerability in the Kong Konnect Model Context Protocol (MCP) server could allow attackers to steal sensitive information by tricking AI assistants. By sending malicious data (like a fake User-Agent) to a public gateway, an attacker can inject hidden instructions that are later read by an AI agent using Kong's analytics tools. If the AI agent is not properly restricted, it might follow these hidden instructions to leak secret credentials, plugin configurations, or internal system details to the attacker.

Vendors: Kong.

Quick answers

Is CVE-2026-13341 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-13341 being exploited in the wild.
How severe is CVE-2026-13341?: High severity, with a CVSS score of 7.4, published 3 July 2026.
Which products and versions are affected?: Kong Mcp-Konnect < 1.0.0.
Is there a fix for CVE-2026-13341?: A patch was published on 2026-07-03: Version 1.0.0 released with fixes Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-13341 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-13341?: Check whether you run Kong Mcp-Konnect at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The Kong Konnect MCP server prior to version 1.0.0 is susceptible to indirect prompt injection via untrusted analytics data and path manipulation in control plane identifiers. Attackers can inject malicious instructions into request metadata (e.g., User-Agent) which is stored in Konnect analytics; when an MCP-connected AI assistant retrieves this data, it may execute the injected prompts. If the AI agent lacks outbound network restrictions, this can result in the exfiltration of secrets, plugin configurations, and operational metadata. Additionally, improper validation of control plane and group identifiers allows for path manipulation, potentially forcing the MCP server to make unauthorized requests to the Konnect API using the user's token. The issue is fixed in version 1.0.0, which introduces input neutralization, UUID validation, and stricter output policies for plugin configurations.

Affected products

KongHQ mcp-konnect < 1.0.0

Timeline

2026-05-15: advisory: GitHub Security Advisory published by Kong
2026-07-03: disclosed: CVE published to NVD
2026-07-03: patched: Version 1.0.0 released with fixes

References

https://github.com/Kong/mcp-konnect/security/advisories/GHSA-7767-3m3w-2p44

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.