cve.bz

CVE-2026-18679 kong inc. kong mesh: Improper Certificate Validation

5.8 mediumEPSS 0.2%Fix available

Medium (5.8) in kong inc. kong mesh. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/kumahq/kuma/v2 2.11.14, 2.12.11, 2.13.7.

On this page
When kuma-dp is started against an HTTPS control plane and the operator did not pass a CA certificate, the data plane connects with TLS peer verification disabled, and the dataplane authentication token is sent over that unverified connection. An on-path actor can intercept the dataplane authentication token and impersonate the control plane to the data plane, injecting a forged bootstrap configuration and taking over the proxy.

Severity

CVSS 4.0

5.8 medium
CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • github.com/kumahq/kuma/v2 (Go): fixed in 2.7.26, 2.9.16, 2.11.14, 2.12.11, 2.13.7

Ask an AI about this CVE

Show the promptExplain CVE-2026-18679 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-18679?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-18679?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-18679 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Kong Inc. Kong Meshbefore 2.7.26
Kong Inc. Kong Meshfrom 2.8.0 before 2.9.16
Kong Inc. Kong Meshfrom 2.10.0 before 2.11.14
Kong Inc. Kong Meshfrom 2.12.0 before 2.12.11
Kong Inc. Kong Meshfrom 2.13.0 before 2.13.7

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-wvmp-6r4v-j6cvGogithub.com/kumahq/kuma/v2<2.7.262.7.26
GHSA-wvmp-6r4v-j6cvGogithub.com/kumahq/kuma/v2>=2.8.0 <2.9.162.9.16
GHSA-wvmp-6r4v-j6cvGogithub.com/kumahq/kuma/v2>=2.10.0 <2.11.142.11.14
GHSA-wvmp-6r4v-j6cvGogithub.com/kumahq/kuma/v2>=2.12.0 <2.12.112.12.11
GHSA-wvmp-6r4v-j6cvGogithub.com/kumahq/kuma/v2>=2.13.0 <2.13.72.13.7
GHSA-wvmp-6r4v-j6cvGogithub.com/kumahq/kuma<=1.8.1no fix published
GO-2026-6013Gogithub.com/kumahq/kumaall versionsno fix published
GO-2026-6013Gogithub.com/kumahq/kuma/v2<2.7.26
>=2.9.13 <2.11.14
>=2.12.4 <2.12.11
>=2.13.0 <2.13.7
2.7.26, 2.11.14, 2.12.11, 2.13.7

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON