CVE-2026-18918

OAuth 1.0 session-fixation chain via unauthenticated provisional-consumer registration and insecure v1_0Allowed default

Published Aug 28, 2026 CVSS 4.0 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

A flaw in Eclipse Lyo permits an attacker to register a provisional OAuth client and immediately elevate it to a trusted client without the required administrative approval. This bypasses the intended authorization logic that protects resources via Lyo’s `AbstractAdapterCredentialsFilter`. The resulting capability lets an unauthenticated attacker access protected APIs and data that should be guarded by full OAuth client validation.

Affected Systems

Vulnerable Eclipse Lyo releases span from 2.0.0 up through 7.0.0. The publicly released v6.0.1.Final contains the vendor‑supplied fix, and the subsequent v7.0.0.Beta3 release also resolves the issue. Any installation of Lyo older than 6.0.1.Final or without this update is at risk.

Risk and Exploitability

With a CVSS score of 9.1 the flaw is considered critical. Although the EPSS score is not available, the high severity and the direct bypass of administrative approval suggest a considerable likelihood of exploitation, especially if the provisional client registration endpoint is reachable. The 3‑legged OAuth flow remains unaffected and rejects provisional clients, but the 2‑legged flow provides a clear attack vector.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Eclipse Lyo to v6.0.1.Final or later to apply the vendor‑provided fix.
  • If an upgrade cannot be performed immediately, disable provisional client registration or enforce administrator approval for all new clients in the OAuth server configuration to prevent unapproved clients from becoming trusted.
  • After applying the patch or configuration change, verify that authorization checks correctly enforce client status and that no client can be marked trusted without explicit approval.

Generated by OpenCVE AI on August 28, 2026 at 13:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Eclipse
Eclipse lyo
Vendors & Products Eclipse
Eclipse lyo
Type Values Removed Values Added
Description 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.
Title OAuth 1.0 session-fixation chain via unauthenticated provisional-consumer registration and insecure v1_0Allowed default
Weaknesses CWE-863
References
Metrics cvssV4_0

{'score': 9.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/AU:Y/R:U/V:C/RE:L/U:Red'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
eclipse
Published
Updated
Aug 31, 2026, 12:27 PM
Reserved
Aug 5, 2026, 7:44 AM
Status
Deferred
Published
Aug 28, 2026, 12:16 PM
Modified
Sep 1, 2026, 9:11 PM