cve.bz

CVE-2026-18676 kong inc. kong mesh: Origin Validation Error

5.1 mediumEPSS 0.3%Fix available

Medium (5.1) in kong inc. kong mesh. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/kumahq/kuma 2.11.13, 2.12.10, 2.13.5.

On this page
The default kuma-cp configuration in Kong Mesh reveals the admin bootstrap token and signing keys to any webpage the operator visits while the control plane is reachable from their browser. Due to a CORS misconfiguration a cross-origin fetch() from a malicious page returns the admin JWT and signing material.

Severity

CVSS 4.0

5.1 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 23rd 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.
CWEs
CWE-346 Origin Validation Error
CWE-942 Permissive Cross-domain Security Policy with Untrusted Domains
OWASP Top 10
A02:2025 Security Misconfiguration, A07:2025 Authentication Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • github.com/kumahq/kuma (Go): fixed in 2.7.25, 2.9.15, 2.11.13, 2.12.10, 2.13.5
  • github.com/kumahq/kuma/v2 (Go): fixed in 2.7.25, 2.11.13, 2.12.10, 2.13.5

Ask an AI about this CVE

Show the promptExplain CVE-2026-18676 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-18676?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-18676?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-18676 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.25
Kong Inc. Kong Meshfrom 2.8.0 before 2.9.15
Kong Inc. Kong Meshfrom 2.10.0 before 2.11.13
Kong Inc. Kong Meshfrom 2.12.0 before 2.12.10
Kong Inc. Kong Meshfrom 2.13.0 before 2.13.5

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-3vcp-chfh-f6r2Gogithub.com/kumahq/kuma<2.7.252.7.25
GHSA-3vcp-chfh-f6r2Gogithub.com/kumahq/kuma>=2.9.0 <2.9.152.9.15
GHSA-3vcp-chfh-f6r2Gogithub.com/kumahq/kuma>=2.11.0 <2.11.132.11.13
GHSA-3vcp-chfh-f6r2Gogithub.com/kumahq/kuma>=2.12.0 <2.12.102.12.10
GHSA-3vcp-chfh-f6r2Gogithub.com/kumahq/kuma>=2.13.0 <2.13.52.13.5
GO-2026-5102Gogithub.com/kumahq/kumaall versionsno fix published
GO-2026-5102Gogithub.com/kumahq/kuma/v2<2.7.25
>=2.9.13 <2.11.13
>=2.12.4 <2.12.10
>=2.13.0 <2.13.5
2.7.25, 2.11.13, 2.12.10, 2.13.5

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-346 (16).

References

Check your stackJSON