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.2%, top 85% 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 — 4 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
15%
KEV
Not listed

Published

August 17, 2026

Last Modified

August 17, 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 16× in last 7d / 16× 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 19:29 UTCGHSA enrichment
  3. 2026-08-20 06:54 UTCGHSA enrichment
  4. 2026-08-19 18:18 UTCEG score recompute
  5. 2026-08-19 18:17 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 05:34 UTCGHSA enrichment
  8. 2026-08-18 16:58 UTCEG score recompute
  9. 2026-08-18 16:58 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 03:57 UTCGHSA enrichment
  12. 2026-08-17 15:20 UTCEG score recompute
  13. 2026-08-17 15:15 UTCEG score recompute
  14. 2026-08-17 13:30 UTCEG score recompute
  15. 2026-08-17 12:22 UTCEG score recompute
  16. 2026-08-17 12:21 UTCMITRE cvelistV5first tracked

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. 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 85.4% 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