CVE-2026-18678

MEDIUMPre-NVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% 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.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

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

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 13, 2026

Advisory Details (3)

Auto-updated Aug 12, 2026
Upstream fix merged — awaiting tagged release. Sources: 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

kumactl 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-v95x-xhq5-4929

Vendor Advisories for CVE-2026-18678(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.7.26—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 29× 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.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 07:34 UTCEG score recompute
  3. 2026-08-20 07:34 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 08:41 UTCEG score recompute
  6. 2026-08-19 08:41 UTCGHSA enrichment
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-18 09:49 UTCEG score recompute
  9. 2026-08-18 09:49 UTCGHSA enrichment
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 10:56 UTCEG score recompute
  12. 2026-08-17 10:56 UTCGHSA enrichment
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 12:04 UTCEG score recompute
  15. 2026-08-16 12:04 UTCGHSA enrichment
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 13:12 UTCEG score recompute
  18. 2026-08-15 13:12 UTCGHSA enrichment
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 14:20 UTCEG score recompute
  21. 2026-08-14 14:20 UTCGHSA enrichment
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 15:27 UTCEG score recompute
  24. 2026-08-13 15:27 UTCGHSA enrichment
  25. 2026-08-13 15:15 UTCEG score recompute
Show 4 more
  1. 2026-08-13 15:15 UTCGHSA enrichment
  2. 2026-08-12 19:19 UTCEG score recompute
  3. 2026-08-12 18:56 UTCEG score recompute
  4. 2026-08-12 18:55 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-18678?
CVE-2026-18678 is a medium vulnerability published on August 12, 2026. 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…
When was CVE-2026-18678 disclosed?
CVE-2026-18678 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18678 actively exploited?
CVE-2026-18678 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 99.2% of all scored CVEs.
What is the CVSS score of CVE-2026-18678?
CVE-2026-18678 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-18678?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18678, 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-18678

Explore →

Is Your Infrastructure Affected by CVE-2026-18678?

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

Start Free Scan →Browse All CVEs