CVE-2026-18918

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

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 (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 28, 2026

Last Modified

September 1, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
Patch available. Sources: github_release.
Web page

[Eclipse Lyo] CVE request for vuln report 693 (#221) · Issues · 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 29× in last 7d / 192× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 335 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 235 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-10-14 02:47 UTCEG score recompute
  3. 2026-10-14 02:47 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  4. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-10-12 22:54 UTCEG score recompute
  6. 2026-10-12 22:53 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  7. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  8. 2026-10-12 16:26 UTCEG score recompute
  9. 2026-10-12 09:26 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  10. 2026-10-11 20:07 UTCEG score recompute
  11. 2026-10-11 17:19 UTCEG score recompute
  12. 2026-10-11 14:52 UTCEG score recompute
  13. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-10-10 13:40 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  16. 2026-10-10 09:39 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  17. 2026-10-10 05:18 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  18. 2026-10-10 00:59 UTCEG score recompute
  19. 2026-10-10 00:59 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  20. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  21. 2026-10-09 07:01 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  22. 2026-10-09 02:43 UTCEG score recompute
  23. 2026-10-09 02:43 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  24. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  25. 2026-10-08 08:24 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
Show 75 more
  1. 2026-10-08 04:39 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  2. 2026-10-08 00:55 UTCEG score recompute
  3. 2026-10-08 00:55 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  4. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  5. 2026-10-07 09:50 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  6. 2026-10-07 05:57 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  7. 2026-10-07 02:12 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  8. 2026-10-06 22:27 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  9. 2026-10-06 18:42 UTCEG score recompute
  10. 2026-10-06 18:42 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  11. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  12. 2026-10-06 14:58 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  13. 2026-10-06 11:13 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  14. 2026-10-06 07:28 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  15. 2026-10-06 00:49 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  16. 2026-10-05 20:34 UTCEG score recompute
  17. 2026-10-05 20:34 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  18. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  19. 2026-10-05 16:50 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  20. 2026-10-05 12:45 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  21. 2026-10-05 09:00 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  22. 2026-10-05 05:06 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  23. 2026-10-05 01:21 UTCEG score recompute
  24. 2026-10-05 01:21 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  25. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  26. 2026-10-04 20:34 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  27. 2026-10-04 16:15 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  28. 2026-10-04 12:30 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  29. 2026-10-04 08:45 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  30. 2026-10-04 04:58 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  31. 2026-10-04 01:14 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  32. 2026-10-03 19:19 UTCEG score recompute
  33. 2026-10-03 19:19 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  34. 2026-10-03 14:20 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  35. 2026-10-03 05:17 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  36. 2026-10-03 01:32 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  37. 2026-10-02 21:34 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  38. 2026-10-02 17:50 UTCEG score recompute
  39. 2026-10-02 17:50 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  40. 2026-10-02 14:01 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  41. 2026-10-02 10:01 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  42. 2026-10-02 06:16 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  43. 2026-10-02 00:37 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  44. 2026-10-01 19:49 UTCEG score recompute
  45. 2026-10-01 19:49 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  46. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  47. 2026-10-01 12:56 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  48. 2026-10-01 09:11 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  49. 2026-10-01 05:27 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  50. 2026-10-01 00:59 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  51. 2026-09-30 19:50 UTCEG score recompute
  52. 2026-09-30 19:50 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  53. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  54. 2026-09-30 11:32 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  55. 2026-09-30 07:37 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  56. 2026-09-30 03:52 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  57. 2026-09-29 16:07 UTCEG score recompute
  58. 2026-09-29 16:07 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  59. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  60. 2026-09-29 12:09 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  61. 2026-09-29 08:22 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  62. 2026-09-29 04:38 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  63. 2026-09-29 00:53 UTCEG score recompute
  64. 2026-09-29 00:53 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  65. 2026-09-28 21:09 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  66. 2026-09-28 14:35 UTCEG score recompute
  67. 2026-09-28 14:35 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  68. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  69. 2026-09-28 10:45 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  70. 2026-09-28 06:46 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  71. 2026-09-28 03:01 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  72. 2026-09-27 23:13 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  73. 2026-09-27 19:28 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL
  74. 2026-09-27 15:42 UTCEG score recompute
  75. 2026-09-27 15:42 UTCGHSA enrichmentGHSA-jhp3-fv3p-rj5c · GitHub severity CRITICAL

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18918?
CVE-2026-18918 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-18918 published?
The CVE record for CVE-2026-18918 was published on August 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 1, 2026; the record at its source may have been updated since.
Is CVE-2026-18918 actively exploited?
CVE-2026-18918 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18918?
CVE-2026-18918 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18918?
A fix for CVE-2026-18918 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-18918 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs