Kong Mesh up to 2.14.1 KDS sync privileges management

Summaryinfo

A vulnerability was found in Kong Mesh up to 2.14.1. It has been classified as problematic. This issue affects some unknown processing of the component KDS sync. Performing a manipulation results in privileges management. This vulnerability was named CVE-2026-18674. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in Kong Mesh up to 2.14.1. It has been classified as problematic. This affects an unknown code block of the component KDS sync. The manipulation with an unknown input leads to a privileges management vulnerability. CWE is classifying the issue as CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

On a Kong Mesh global control plane, resources received over the zone-to-global KDS sync are attributed using the in-band, sender-controlled ControlPlane.Identifier rather than the authenticated zone identity derived from the connection. Authenticated zones can have the global control plane store and re-distribute those resources as belonging to another zone. The result is a cross-zone isolation bypass: the holder of a single enrolled zone's credential can inject, attribute, and overwrite resources in another zone's namespace mesh-wide. The root cause lives in Kuma's open-source KDS sync code, which Kong Mesh's control plane is built on.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-18674 since 08/03/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Additional levels of successful authentication are necessary for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

Upgrading to version 2.7.29, 2.9.19, 2.11.18, 2.12.14, 2.13.10 or 2.14.2 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• Kong

Name

• Mesh

Version

• 2.7.0
• 2.7.1
• 2.7.2
• 2.7.3
• 2.7.4
• 2.7.5
• 2.7.6
• 2.7.7
• 2.7.8
• 2.7.9
• 2.7.10
• 2.7.11
• 2.7.12
• 2.7.13
• 2.7.14
• 2.7.15
• 2.7.16
• 2.7.17
• 2.7.18
• 2.7.19
• 2.7.20
• 2.7.21
• 2.7.22
• 2.7.23
• 2.7.24
• 2.7.25
• 2.7.26
• 2.7.27
• 2.7.28
• 2.9.0
• 2.9.1
• 2.9.2
• 2.9.3
• 2.9.4
• 2.9.5
• 2.9.6
• 2.9.7
• 2.9.8
• 2.9.9
• 2.9.10
• 2.9.11
• 2.9.12
• 2.9.13
• 2.9.14
• 2.9.15
• 2.9.16
• 2.9.17
• 2.9.18
• 2.11.0
• 2.11.1
• 2.11.2
• 2.11.3
• 2.11.4
• 2.11.5
• 2.11.6
• 2.11.7
• 2.11.8
• 2.11.9
• 2.11.10
• 2.11.11
• 2.11.12
• 2.11.13
• 2.11.14
• 2.11.15
• 2.11.16
• 2.11.17
• 2.12.0
• 2.12.1
• 2.12.2
• 2.12.3
• 2.12.4
• 2.12.5
• 2.12.6
• 2.12.7
• 2.12.8
• 2.12.9
• 2.12.10
• 2.12.11
• 2.12.12
• 2.12.13
• 2.13.0
• 2.13.1
• 2.13.2
• 2.13.3
• 2.13.4
• 2.13.5
• 2.13.6
• 2.13.7
• 2.13.8
• 2.13.9
• 2.14.0
• 2.14.1

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion