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.3%, top 76% 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
6.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.0Exploit: None knownExposed: 0

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

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

Published

August 12, 2026

Last Modified

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

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 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-18677 actively exploited?
CVE-2026-18677 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 75.8% of all scored CVEs.
What is the CVSS score of CVE-2026-18677?
CVE-2026-18677 has a CVSS v3 base score of 6.0 (NVD).
How do I remediate CVE-2026-18677?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18677, 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-18677

Explore →

Is Your Infrastructure Affected by CVE-2026-18677?

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

Start Free Scan →Browse All CVEs