Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-18678Kong Mesh: kumactl connects to the control plane without verifying the TLS certificate when no CA is configured

Description

When an operator adds an HTTPS control plane profile to kumactl without providing a CA certificate, kumactl disables TLS verification and sends API tokens over the unverified connection. An attacker on the network path between the operator and the control plane can intercept user or admin API tokens and then act against the control plane as that user.

Timeline

  1. ID reserved

    By Kong

  2. · 9 days later

    Published

  3. · 1 day later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-18678, by who scored it
Scored byCVSSScoreVector
KongCNA (assigner)4.0Medium5.5CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H
NVDNVD · Awaiting Analysis4.0Medium5.5CVSS:4.0/AV:A/AC:H/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS (exploitation in 30 days)
0.13% · top 98% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Kong Inc. · Kong Mesh

    • affected < 2.7.26
    • affected 2.8.0 – < 2.9.16
    • affected 2.10.0 – < 2.11.14
    • affected 2.12.0 – < 2.12.11
    • affected 2.13.0 – < 2.13.7

What to do

Solution: Upgrade to Kong Mesh 2.7.26, 2.9.16, 2.11.14, 2.12.11 or 2.13.7, whichever matches your release line. Patched releases fall back to the operating system trust store instead of disabling verification, so a publicly trusted control plane certificate verifies with no further configuration. The 2.14 line shipped after the fix and was never affected.

Workaround: When adding an HTTPS control plane profile to kumactl, always pass --ca-cert-file pointing at the control plane's serving CA. Alternatively terminate the control plane behind a publicly trusted certificate.

References

References3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-18678 badge
[![CVE-2026-18678](https://cveledger.app/badge/CVE-2026-18678.svg)](https://cveledger.app/cve/CVE-2026-18678)

Record last updated .