CVE-2026-92611

MEDIUMPre-NVD 4.84.8—
EchelonGraph scoreMEDIUM confidence

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

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

In Eclipse Ankaios versions 0.6.0 to before 1.0.4, LogRule::matches in the agent control-interface authorizer stops at the first wildcard pattern in a single rule instead of evaluating later entries, which can cause deny LogRule entries to be skipped and allow unauthorized access to another workload's logs.

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

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (3)

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

Fix error with wildcard matching for log access rules

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

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

v1.0.4

Patch available: eclipse-ankaios/ankaios v1.0.4

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

[Eclipse Ankaios] Ankaios LogRule authorization bypass (#308) · Issues · Eclipse Projects Security / cve-assignment · GitLab

https://gitlab.eclipse.org/security/cve-assignment/-/work_items/308

Vendor Advisories for CVE-2026-92611(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 11× in last 7d / 11× 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-18 19:48 UTCEG score recompute
  2. 2026-09-18 19:48 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 12:28 UTCGHSA enrichment
  5. 2026-09-17 13:21 UTCEG score recompute
  6. 2026-09-17 13:21 UTCGHSA enrichment
  7. 2026-09-17 12:50 UTCEG score recompute
  8. 2026-09-17 12:49 UTCGHSA enrichment
  9. 2026-09-17 11:20 UTCEG score recompute
  10. 2026-09-17 10:45 UTCEG score recompute
  11. 2026-09-17 10:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92611?
CVE-2026-92611 is a medium vulnerability published on September 17, 2026. In Eclipse Ankaios versions 0.6.0 to before 1.0.4, LogRule::matches in the agent control-interface authorizer stops at the first wildcard pattern in a single rule instead of evaluating later entries, which can cause deny LogRule entries to be skipped and allow unauthorized access to another…
When was CVE-2026-92611 disclosed?
CVE-2026-92611 was first published in the National Vulnerability Database on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92611 actively exploited?
CVE-2026-92611 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 88.4% of all scored CVEs.
What is the CVSS score of CVE-2026-92611?
CVE-2026-92611 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-92611?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92611, 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-92611

Explore →

Is Your Infrastructure Affected by CVE-2026-92611?

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

Start Free Scan →Browse All CVEs