CVE-2026-18674

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 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
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

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

On a Kong Mesh global control plane, resources received over the zone-to-global KDS sync are attributed using the in-band, sender-controlled ControlPlane.Identifier rather than the authenticated zone identity derived from the connection. Authenticated zones can have the global control plane store and re-distribute those resources as belonging to another zone.

The result is a cross-zone isolation bypass: the holder of a single enrolled zone's credential can inject, attribute, and overwrite resources in another zone's namespace mesh-wide.

The root cause lives in Kuma's open-source KDS sync code, which Kong Mesh's control plane is built on.

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

Published

August 17, 2026

Last Modified

August 31, 2026

Advisory Details (9)

Auto-updated Aug 17, 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(kds): attribute zone-to-global synced resources by the connecting zone's client-id (backport of #17456)

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

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

fix(kds): attribute zone-to-global synced resources by the connecting zone's client-id (backport of #17456)

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

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

fix(kds): attribute zone-to-global synced resources by the connecting zone's client-id (backport of #17456)

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

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

fix(kds): attribute zone-to-global synced resources by the connecting zone's client-id (backport of #17456)

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

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

fix(kds): attribute zone-to-global synced resources by the connecting zone's client-id (backport of #17456)

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

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

fix(kds): attribute zone-to-global synced resources by the connecting zone's client-id (backport of #17456)

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

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

fix(kds): attribute zone-to-global synced resources by the connecting zone's client-id

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

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

Multi-zone Kuma: global control plane attributes KDS-synced resources by an unvalidated in-band zone identifier · Advisory · kumahq/kuma · GitHub

https://github.com/kumahq/kuma/security/advisories/GHSA-m58j-fjmc-h3g4

Vendor Advisories for CVE-2026-18674(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 23× in last 7d / 106× 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 121 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18674?
CVE-2026-18674 is a high vulnerability published on August 17, 2026. On a Kong Mesh global control plane, resources received over the zone-to-global KDS sync are attributed using the in-band, sender-controlled ControlPlane.Identifier rather than the authenticated zone identity derived from the connection. Authenticated zones can have the global control plane store…
When was CVE-2026-18674 disclosed?
CVE-2026-18674 was first published in the National Vulnerability Database on August 17, 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-18674 actively exploited?
CVE-2026-18674 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 67.9% of all scored CVEs.
What is the CVSS score of CVE-2026-18674?
CVE-2026-18674 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-18674?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18674, 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-18674

Explore →

Is Your Infrastructure Affected by CVE-2026-18674?

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

Start Free Scan →Browse All CVEs