CVE-2026-18675

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

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

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

The dataplane token validator in kuma-cp performs an unchecked Go type assertion on the JWT kid header. A token whose kid is a JSON number decodes as a float64 and triggers a runtime panic before any signature, claims, or authorization check runs.

The panic terminates the entire kuma-cp process, HTTP API, the health and readiness endpoints, and xDS. Unauthenticated access to the dataplane gRPC server can trigger the crash with a malformed token

A single request is a transient interruption; sustaining an outage requires repeated requests.

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

Published

August 12, 2026

Last Modified

August 13, 2026

Advisory Details (9)

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

Kong Mesh changelog - Kong Mesh | Kong Docs

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

fix(tokens): reject a non-string kid header and recover from dp-server handler panics (backport of #17465)

Patch available: kumahq/kuma v2.7.29 (PR #17472 merged 2026-07-17)

https://github.com/kumahq/kuma/pull/17472
github_pr Patch Available

fix(tokens): reject a non-string kid header and recover from dp-server handler panics (backport of #17465)

Patch available: kumahq/kuma 2.9.19 (PR #17470 merged 2026-07-17)

https://github.com/kumahq/kuma/pull/17470
github_pr Patch Available

fix(tokens): reject a non-string kid header and recover from dp-server handler panics (backport of #17465)

Patch available: kumahq/kuma v2.11.18 (PR #17469 merged 2026-07-17)

https://github.com/kumahq/kuma/pull/17469
github_pr Patch Available

fix(tokens): reject a non-string kid header and recover from dp-server handler panics (backport of #17465)

Patch available: kumahq/kuma v2.12.14 (PR #17471 merged 2026-07-17)

https://github.com/kumahq/kuma/pull/17471
github_pr Patch Available

fix(tokens): reject a non-string kid header and recover from dp-server handler panics (backport of #17465)

Patch available: kumahq/kuma v2.13.10 (PR #17467 merged 2026-07-17)

https://github.com/kumahq/kuma/pull/17467
github_pr Patch Available

fix(tokens): reject a non-string kid header and recover from dp-server handler panics (backport of #17465)

Patch available: kumahq/kuma v2.14.2 (PR #17468 merged 2026-07-17)

https://github.com/kumahq/kuma/pull/17468
github_pr

fix(tokens): reject a non-string kid header and recover from dp-server handler panics

Fix merged in kumahq/kuma PR #17465 on 2026-07-17 — awaiting tagged release

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

Kuma control-plane denial of service via a malformed xDS dataplane token with a non-string JWT kid · Advisory · kumahq/kuma · GitHub

https://github.com/kumahq/kuma/security/advisories/GHSA-5mxq-7xq4-3vx8

Vendor Advisories for CVE-2026-18675(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 28× 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 21:23 UTCGHSA enrichment
  3. 2026-08-19 20:46 UTCEG score recompute
  4. 2026-08-19 20:46 UTCGHSA enrichment
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 20:08 UTCEG score recompute
  7. 2026-08-18 20:08 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 19:29 UTCEG score recompute
  10. 2026-08-17 19:29 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 18:49 UTCEG score recompute
  13. 2026-08-16 18:49 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 17:59 UTCEG score recompute
  17. 2026-08-15 17:59 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 17:21 UTCEG score recompute
  20. 2026-08-14 17:21 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 16:30 UTCEG score recompute
  23. 2026-08-13 16:30 UTCGHSA enrichment
  24. 2026-08-13 15:34 UTCEG score recompute
  25. 2026-08-13 15:34 UTCGHSA enrichment
Show 3 more
  1. 2026-08-12 19:19 UTCEG score recompute
  2. 2026-08-12 18:56 UTCEG score recompute
  3. 2026-08-12 18:55 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18675?
CVE-2026-18675 is a medium vulnerability published on August 12, 2026. The dataplane token validator in kuma-cp performs an unchecked Go type assertion on the JWT kid header. A token whose kid is a JSON number decodes as a float64 and triggers a runtime panic before any signature, claims, or authorization check runs. The panic terminates the entire kuma-cp process,…
When was CVE-2026-18675 disclosed?
CVE-2026-18675 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-18675 actively exploited?
CVE-2026-18675 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 68.2% of all scored CVEs.
What is the CVSS score of CVE-2026-18675?
CVE-2026-18675 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-18675?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18675, 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

Explore the affected products and dependency analysis for CVE-2026-18675

Explore →

Is Your Infrastructure Affected by CVE-2026-18675?

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

Start Free Scan →Browse All CVEs