CVE-2026-18676

MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreMEDIUM confidence

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

A fix is available — apply it.

The default kuma-cp configuration in Kong Mesh reveals the admin bootstrap token and signing keys to any webpage the operator visits while the control plane is reachable from their browser. Due to a CORS misconfiguration a cross-origin fetch() from a malicious page returns the admin JWT and signing material.

CVSS v3
5.1
EG Score
5.1MEDIUMmedium confidence
EG Risk
23
EG Risk 23/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
Severity51% × 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.3%
EPSS %ILE
20th
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 (8)

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 Patch Available

fix(api-server): harden localhost admin auth (backport of #16416)

Patch available: kumahq/kuma v2.13.5 (PR #16427 merged 2026-04-28)

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

fix(api-server): harden localhost admin auth (backport of #16416)

Patch available: kumahq/kuma v2.7.26 (PR #16426 merged 2026-04-28)

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

fix(api-server): harden localhost admin auth (backport of #16416)

Patch available: kumahq/kuma v2.11.13 (PR #16425 merged 2026-04-28)

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

fix(api-server): harden localhost admin auth (backport of #16416)

Patch available: kumahq/kuma 2.9.15 (PR #16424 merged 2026-04-28)

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

fix(api-server): harden localhost admin auth (backport of #16416)

Patch available: kumahq/kuma v2.12.10 (PR #16423 merged 2026-04-28)

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

fix(api-server): harden localhost admin auth

Fix merged in kumahq/kuma PR #16416 on 2026-04-27 — awaiting tagged release

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

Default kuma-cp leaks admin token cross-origin via CORS wildcard + LocalhostIsAdmin · Advisory · kumahq/kuma · GitHub

https://github.com/kumahq/kuma/security/advisories/GHSA-3vcp-chfh-f6r2

Vendor Advisories for CVE-2026-18676(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 rangeFix by version rangeDependents
github.com/kumahq/kuma—
  • every version up to 2.7.25: fixed in 2.7.25
  • 2.9.0 up to 2.9.15: fixed in 2.9.15
  • 2.11.0 up to 2.11.13: fixed in 2.11.13
  • 2.12.0 up to 2.12.10: fixed in 2.12.10
  • 2.13.0 up to 2.13.5: fixed in 2.13.5
  • every version on: no fix on record
—
github.com/kumahq/kuma/v2—
  • every version up to 2.7.25: fixed in 2.7.25
  • 2.9.13 up to 2.11.13: fixed in 2.11.13
  • 2.12.4 up to 2.12.10: fixed in 2.12.10
  • 2.13.0 up to 2.13.5: fixed in 2.13.5
—

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-18676?
CVE-2026-18676 is a medium vulnerability published on August 12, 2026. The default kuma-cp configuration in Kong Mesh reveals the admin bootstrap token and signing keys to any webpage the operator visits while the control plane is reachable from their browser. Due to a CORS misconfiguration a cross-origin fetch() from a malicious page returns the admin JWT and signing…
When was CVE-2026-18676 disclosed?
CVE-2026-18676 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-18676 actively exploited?
CVE-2026-18676 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18676?
CVE-2026-18676 has a CVSS base score of 5.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18676?
A fix for CVE-2026-18676 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-18676 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-18676?

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

Book a Demo →Browse All CVEs