CVE-2026-18677

MEDIUMPre-NVD 6.06.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (34th percentile of EPSS-scored CVEs). 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
6.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In Kong Mesh running in universal mode with a MeshIdentity whose SPIFFE ID path template derives from the dataplane's kuma.io/workload label, the XDS authenticator in kuma-cp validates that label only when the dataplane token is bound to a workload. Workload binding is optional, so a dataplane presenting a tags-bound token can register with kuma.io/workload set to any value and obtain another workload's SPIFFE identity.

CVSS v3
6.0
EG Score
6.0MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100CISA SSVC

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
Severity60% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
34th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 12, 2026

Last Modified

August 31, 2026

Advisory Details (5)

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(auth): require workload-bound token for workload-derived identity (backport of #17474)

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

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

fix(auth): require workload-bound token for workload-derived identity (backport of #17474)

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

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

fix(auth): require workload-bound token for workload-derived identity

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

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

Dataplane token without a workload binding can claim any workload's SPIFFE identity (universal + MeshIdentity) · Advisory · kumahq/kuma · GitHub

https://github.com/kumahq/kuma/security/advisories/GHSA-744g-c785-x65q

Vendor Advisories for CVE-2026-18677(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 62× 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 129 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18677?
CVE-2026-18677 is a medium vulnerability published on August 12, 2026. In Kong Mesh running in universal mode with a MeshIdentity whose SPIFFE ID path template derives from the dataplane's kuma.io/workload label, the XDS authenticator in kuma-cp validates that label only when the dataplane token is bound to a workload. Workload binding is optional, so a dataplane…
When was CVE-2026-18677 disclosed?
CVE-2026-18677 was first published 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-18677 actively exploited?
CVE-2026-18677 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18677?
CVE-2026-18677 has a CVSS base score of 6.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18677?
A fix for CVE-2026-18677 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-18677 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-18677?

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

Book a Demo →Browse All CVEs