CVE-2026-18679

MEDIUMPre-NVD 5.85.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
5.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.8
EG Score
5.8(medium)
EG Risk
26(Track)
EG Risk 26/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity58% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 31, 2026

Advisory Details (3)

Auto-updated Aug 12, 2026
Patch available. Sources: github, github_pr.
generic

Kong Mesh changelog - Kong Mesh | Kong Docs

https://developer.konghq.com/mesh/changelog/
github_pr

fix(kuma-cp): use system trust when CA cert is not provided

Fix merged in kumahq/kuma PR #16777 on 2026-05-29 — awaiting tagged release

https://github.com/kumahq/kuma/pull/16777
github Patch Available

kuma-dp connects to control plane without verifying TLS certificate when no CA is configured · Advisory · kumahq/kuma · GitHub

https://github.com/kumahq/kuma/security/advisories/GHSA-wvmp-6r4v-j6cv

Vendor Advisories for CVE-2026-18679(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/kumahq/kuma———
github.com/kumahq/kuma/v2—2.13.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 76× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 104 total refreshes for this CVE.

  1. 2026-09-18 22:49 UTCEG score recompute
  2. 2026-09-18 22:49 UTCGHSA enrichment
  3. 2026-09-18 19:27 UTCEPSS rescore
  4. 2026-09-18 00:31 UTCEG score recompute
  5. 2026-09-18 00:31 UTCGHSA enrichment
  6. 2026-09-17 00:20 UTCEG score recompute
  7. 2026-09-17 00:20 UTCGHSA enrichment
  8. 2026-09-16 14:07 UTCEPSS rescore
  9. 2026-09-16 05:14 UTCEPSS rescore
  10. 2026-09-15 20:17 UTCEG score recompute
  11. 2026-09-15 20:17 UTCGHSA enrichment
  12. 2026-09-14 21:55 UTCGHSA enrichment
  13. 2026-09-13 21:26 UTCEG score recompute
  14. 2026-09-13 21:26 UTCGHSA enrichment
  15. 2026-09-13 16:46 UTCEPSS rescore
  16. 2026-09-12 23:09 UTCEG score recompute
  17. 2026-09-12 23:09 UTCGHSA enrichment
  18. 2026-09-12 15:00 UTCEPSS rescore
  19. 2026-09-12 00:10 UTCEG score recompute
  20. 2026-09-12 00:09 UTCGHSA enrichment
  21. 2026-09-11 14:52 UTCEPSS rescore
  22. 2026-09-11 09:36 UTCEPSS rescore
  23. 2026-09-11 01:49 UTCEG score recompute
  24. 2026-09-11 01:49 UTCGHSA enrichment
  25. 2026-09-10 09:34 UTCEPSS rescore
Show 75 more
  1. 2026-09-10 03:31 UTCGHSA enrichment
  2. 2026-09-09 05:14 UTCEG score recompute
  3. 2026-09-09 05:14 UTCGHSA enrichment
  4. 2026-09-08 22:00 UTCEPSS rescore
  5. 2026-09-07 19:33 UTCEG score recompute
  6. 2026-09-07 19:33 UTCGHSA enrichment
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 21:16 UTCEG score recompute
  9. 2026-09-06 21:16 UTCGHSA enrichment
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-05 22:59 UTCEG score recompute
  12. 2026-09-05 22:59 UTCGHSA enrichment
  13. 2026-09-05 00:41 UTCEG score recompute
  14. 2026-09-05 00:41 UTCGHSA enrichment
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-03 23:16 UTCGHSA enrichment
  17. 2026-09-02 23:29 UTCEG score recompute
  18. 2026-09-02 23:29 UTCGHSA enrichment
  19. 2026-09-02 14:11 UTCEPSS rescore
  20. 2026-09-01 17:54 UTCEG score recompute
  21. 2026-09-01 17:54 UTCGHSA enrichment
  22. 2026-09-01 13:53 UTCEPSS rescore
  23. 2026-09-01 04:39 UTCEPSS rescore
  24. 2026-08-31 19:34 UTCGHSA enrichment
  25. 2026-08-31 11:46 UTCEG score recompute
  26. 2026-08-31 11:46 UTCGHSA enrichment
  27. 2026-08-30 19:17 UTCEPSS rescore
  28. 2026-08-30 13:29 UTCGHSA enrichment
  29. 2026-08-29 15:11 UTCEG score recompute
  30. 2026-08-29 15:11 UTCGHSA enrichment
  31. 2026-08-28 21:41 UTCEPSS rescore
  32. 2026-08-28 13:26 UTCGHSA enrichment
  33. 2026-08-27 14:46 UTCEG score recompute
  34. 2026-08-27 14:46 UTCGHSA enrichment
  35. 2026-08-27 14:25 UTCEPSS rescore
  36. 2026-08-26 16:28 UTCEG score recompute
  37. 2026-08-26 16:28 UTCGHSA enrichment
  38. 2026-08-26 14:46 UTCEPSS rescore
  39. 2026-08-25 17:15 UTCEG score recompute
  40. 2026-08-25 17:15 UTCGHSA enrichment
  41. 2026-08-25 13:48 UTCEPSS rescore
  42. 2026-08-24 18:58 UTCEG score recompute
  43. 2026-08-24 18:57 UTCGHSA enrichment
  44. 2026-08-23 20:40 UTCGHSA enrichment
  45. 2026-08-22 22:23 UTCGHSA enrichment
  46. 2026-08-22 00:06 UTCEG score recompute
  47. 2026-08-22 00:06 UTCGHSA enrichment
  48. 2026-08-21 23:49 UTCEPSS rescore
  49. 2026-08-21 01:49 UTCEG score recompute
  50. 2026-08-21 01:48 UTCGHSA enrichment
  51. 2026-08-20 22:55 UTCEPSS rescore
  52. 2026-08-20 03:30 UTCEG score recompute
  53. 2026-08-20 03:30 UTCGHSA enrichment
  54. 2026-08-19 17:03 UTCEPSS rescore
  55. 2026-08-19 05:12 UTCEG score recompute
  56. 2026-08-19 05:12 UTCGHSA enrichment
  57. 2026-08-18 13:48 UTCEPSS rescore
  58. 2026-08-18 06:53 UTCEG score recompute
  59. 2026-08-18 06:53 UTCGHSA enrichment
  60. 2026-08-17 13:47 UTCEPSS rescore
  61. 2026-08-17 08:36 UTCEG score recompute
  62. 2026-08-17 08:36 UTCGHSA enrichment
  63. 2026-08-16 14:56 UTCEPSS rescore
  64. 2026-08-16 10:19 UTCEG score recompute
  65. 2026-08-16 10:19 UTCGHSA enrichment
  66. 2026-08-16 02:14 UTCEPSS rescore
  67. 2026-08-15 12:02 UTCEG score recompute
  68. 2026-08-15 12:02 UTCGHSA enrichment
  69. 2026-08-15 01:30 UTCEPSS rescore
  70. 2026-08-14 13:44 UTCEG score recompute
  71. 2026-08-14 13:44 UTCGHSA enrichment
  72. 2026-08-13 22:00 UTCEPSS rescore
  73. 2026-08-13 15:27 UTCEG score recompute
  74. 2026-08-13 15:27 UTCGHSA enrichment
  75. 2026-08-13 15:15 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-18679?
CVE-2026-18679 is a medium vulnerability published on August 12, 2026. 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…
When was CVE-2026-18679 disclosed?
CVE-2026-18679 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18679 actively exploited?
CVE-2026-18679 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.0% of all scored CVEs.
What is the CVSS score of CVE-2026-18679?
CVE-2026-18679 has a CVSS v3 base score of 5.8 (NVD).
How do I remediate CVE-2026-18679?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18679, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-18679

Explore →

Is Your Infrastructure Affected by CVE-2026-18679?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs