CVE-2026-18918

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% 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
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: None knownExposed: 0

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

In Eclipse Lyo versions 2.0.0 to 7.0.0, OAuth server authorization checks can be bypassed when the 2-legged auth is supported by the server. In those cases, application that based their authz filters upon Lyo-provided AbstractAdapterCredentialsFilter, are vulnerable. An attacked can create a provisional trusted client (valid use-case) but then it can be used as a trusted client immediately without requiring the administrator approval to clear the provisional status. The 3-legged path requiring user interaction is not vulnerable and rejects provisional clients.

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

Published

August 28, 2026

Last Modified

August 28, 2026

Advisory Details (3)

Auto-updated Aug 29, 2026
Patch available. Sources: github_release.
generic

Eclipse Projects Security / cve-assignment · GitLab

https://gitlab.eclipse.org/security/cve-assignment/-/work_items/221
github_release Patch Available

v7.0.0.Beta3

Patch available: eclipse-lyo/lyo v7.0.0.Beta3 (pre-release)

https://github.com/eclipse-lyo/lyo/releases/tag/v7.0.0.Beta3
github_release Patch Available

v6.0.1.Final security release

Patch available: eclipse-lyo/lyo v6.0.1.Final

https://github.com/eclipse-lyo/lyo/releases/tag/v6.0.1.Final

Vendor Advisories for CVE-2026-18918(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 18× in last 7d / 18× 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-30 06:01 UTCGHSA enrichment
  2. 2026-08-30 02:16 UTCEG score recompute
  3. 2026-08-30 02:16 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-29 22:31 UTCGHSA enrichment
  6. 2026-08-29 18:47 UTCGHSA enrichment
  7. 2026-08-29 15:00 UTCGHSA enrichment
  8. 2026-08-29 11:14 UTCGHSA enrichment
  9. 2026-08-29 07:27 UTCGHSA enrichment
  10. 2026-08-29 03:37 UTCGHSA enrichment
  11. 2026-08-28 23:50 UTCGHSA enrichment
  12. 2026-08-28 16:36 UTCEG score recompute
  13. 2026-08-28 16:36 UTCGHSA enrichment
  14. 2026-08-28 15:39 UTCEG score recompute
  15. 2026-08-28 15:39 UTCGHSA enrichment
  16. 2026-08-28 12:23 UTCEG score recompute
  17. 2026-08-28 11:25 UTCEG score recompute
  18. 2026-08-28 11:19 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18918?
CVE-2026-18918 is a critical vulnerability published on August 28, 2026. In Eclipse Lyo versions 2.0.0 to 7.0.0, OAuth server authorization checks can be bypassed when the 2-legged auth is supported by the server. In those cases, application that based their authz filters upon Lyo-provided AbstractAdapterCredentialsFilter, are vulnerable. An attacked can create a…
When was CVE-2026-18918 disclosed?
CVE-2026-18918 was first published in the National Vulnerability Database on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-18918 actively exploited?
CVE-2026-18918 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 69.8% of all scored CVEs.
What is the CVSS score of CVE-2026-18918?
CVE-2026-18918 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-18918?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-18918, 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-18918

Explore →

Is Your Infrastructure Affected by CVE-2026-18918?

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

Start Free Scan →Browse All CVEs