CVE-2026-84173

HIGHPre-NVD 8.38.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% 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 weekElevated
8.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.3Exploit: Elevated riskExposed: 0

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

In Eclipse Ankaios versions v0.5.1 through v1.0.1, the agent-side Control Interface authorizer incorrectly evaluates multi-segment allow rules whose first path segment is a wildcard. An authenticated workload with access restricted by such a rule can submit a CompleteStateRequest or UpdateStateRequest with an empty field mask. The request may then be incorrectly authorized as matching the scoped rule, allowing the workload to read the complete cluster state or replace state outside its authorized subtree. This may result in unauthorized disclosure or modification of other workloads and cluster configuration. Only a rule consisting solely of * is intended to authorize an empty mask.

Mitigation: Until an update containing the fix is installed, avoid multi-segment Control Interface allow-rule filter masks that begin with a wildcard, such as *.workloads.some_workload. Replace them with explicit paths such as desiredState.workloads.some_workload, where applicable. A filter mask consisting solely of * has different, intentionally unrestricted semantics and should only be used when full-state access is intended.

CVSS v3
8.3
EG Score
8.3(medium)
EG Risk
53(Track*)
EG Risk 53/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
Severity83% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

September 7, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Sep 7, 2026
Patch available. Sources: github_release, github_pr.
github_pr

Prevent scoped wildcard rules from matching empty paths

Fix merged in eclipse-ankaios/ankaios PR #790 on 2026-09-04 — awaiting tagged release

https://github.com/eclipse-ankaios/ankaios/pull/790
github_release Patch Available

v1.0.2

Patch available: eclipse-ankaios/ankaios v1.0.2

https://github.com/eclipse-ankaios/ankaios/releases/tag/v1.0.2
generic

[Eclipse Ankaios] Security vulnerability in Eclipse Ankaios Control Interface Workload Authorization (#853) · Issues · Eclipse Projects Security / vulnerability-reports · GitLab

https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/853

Vendor Advisories for CVE-2026-84173(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 24× in last 7d / 68× 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-09-25 01:53 UTCEG score recompute
  2. 2026-09-25 01:53 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-24 12:51 UTCGHSA enrichment
  5. 2026-09-23 23:50 UTCGHSA enrichment
  6. 2026-09-23 10:48 UTCGHSA enrichment
  7. 2026-09-22 21:47 UTCEG score recompute
  8. 2026-09-22 21:47 UTCGHSA enrichment
  9. 2026-09-22 16:01 UTCEPSS rescore
  10. 2026-09-22 08:46 UTCEG score recompute
  11. 2026-09-22 08:46 UTCGHSA enrichment
  12. 2026-09-21 21:09 UTCEPSS rescore
  13. 2026-09-21 19:44 UTCGHSA enrichment
  14. 2026-09-21 06:43 UTCEG score recompute
  15. 2026-09-21 06:42 UTCGHSA enrichment
  16. 2026-09-20 20:16 UTCEPSS rescore
  17. 2026-09-20 17:41 UTCGHSA enrichment
  18. 2026-09-20 04:40 UTCEG score recompute
  19. 2026-09-20 04:40 UTCGHSA enrichment
  20. 2026-09-19 15:38 UTCGHSA enrichment
  21. 2026-09-19 02:34 UTCEG score recompute
  22. 2026-09-19 02:34 UTCGHSA enrichment
  23. 2026-09-18 19:28 UTCEPSS rescore
  24. 2026-09-18 13:32 UTCGHSA enrichment
  25. 2026-09-18 00:31 UTCEG score recompute
Show 43 more
  1. 2026-09-18 00:31 UTCGHSA enrichment
  2. 2026-09-17 19:32 UTCEPSS rescore
  3. 2026-09-17 11:30 UTCGHSA enrichment
  4. 2026-09-16 22:29 UTCEG score recompute
  5. 2026-09-16 22:29 UTCGHSA enrichment
  6. 2026-09-16 14:09 UTCEPSS rescore
  7. 2026-09-16 08:59 UTCEG score recompute
  8. 2026-09-16 08:59 UTCGHSA enrichment
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 18:41 UTCGHSA enrichment
  11. 2026-09-15 05:33 UTCEG score recompute
  12. 2026-09-15 05:33 UTCGHSA enrichment
  13. 2026-09-15 03:12 UTCEPSS rescore
  14. 2026-09-15 03:12 UTCEPSS rescore
  15. 2026-09-14 16:20 UTCGHSA enrichment
  16. 2026-09-14 03:18 UTCEG score recompute
  17. 2026-09-14 03:18 UTCGHSA enrichment
  18. 2026-09-13 14:17 UTCGHSA enrichment
  19. 2026-09-13 01:16 UTCGHSA enrichment
  20. 2026-09-12 12:15 UTCGHSA enrichment
  21. 2026-09-11 23:14 UTCEG score recompute
  22. 2026-09-11 23:14 UTCGHSA enrichment
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-11 09:53 UTCEG score recompute
  26. 2026-09-11 09:53 UTCGHSA enrichment
  27. 2026-09-10 20:51 UTCEG score recompute
  28. 2026-09-10 20:51 UTCGHSA enrichment
  29. 2026-09-10 07:50 UTCGHSA enrichment
  30. 2026-09-09 18:49 UTCGHSA enrichment
  31. 2026-09-09 05:48 UTCEG score recompute
  32. 2026-09-09 05:48 UTCGHSA enrichment
  33. 2026-09-08 22:01 UTCEPSS rescore
  34. 2026-09-08 16:47 UTCEG score recompute
  35. 2026-09-08 16:46 UTCGHSA enrichment
  36. 2026-09-08 16:00 UTCEG score recompute
  37. 2026-09-08 16:00 UTCGHSA enrichment
  38. 2026-09-08 14:57 UTCGHSA enrichment
  39. 2026-09-08 12:38 UTCGHSA enrichment
  40. 2026-09-07 23:24 UTCGHSA enrichment
  41. 2026-09-07 10:20 UTCEG score recompute
  42. 2026-09-07 09:48 UTCEG score recompute
  43. 2026-09-07 09:46 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-84173?
CVE-2026-84173 is a high vulnerability published on September 7, 2026. In Eclipse Ankaios versions v0.5.1 through v1.0.1, the agent-side Control Interface authorizer incorrectly evaluates multi-segment allow rules whose first path segment is a wildcard. An authenticated workload with access restricted by such a rule can submit a CompleteStateRequest or…
When was CVE-2026-84173 disclosed?
CVE-2026-84173 was first published in the National Vulnerability Database on September 7, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84173 actively exploited?
CVE-2026-84173 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 95.2% of all scored CVEs.
What is the CVSS score of CVE-2026-84173?
CVE-2026-84173 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-84173?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-84173, 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-84173

Explore →

Is Your Infrastructure Affected by CVE-2026-84173?

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