Description
In Eclipse Vert.x versions [4.0.0, 4.5.34] or [5.0.0,5.0.12] or [5.1.0,5.1.9] or [5.2.0, 5.2.0], a scope bypass vulnerability exists in Eclipse Vert.x Web's ChainAuthHandler when used with scope-requiring authentication handlers such as JWTAuthHandler or OAuth2AuthHandler. When a user is already authenticated on the routing context by a preceding handler in the request pipeline, ChainAuthHandler skips all scope validation configured via withScope() or withScopes(). This affects both any() and all() chain modes.



The root cause is that postAuthentication() relies on internal state that is only set during the authenticate() phase, which is skipped entirely for pre-authenticated users. In any() mode, the absence of this state causes the method to fall through without delegating scope checks to any handler. In all() mode, scope checks are unconditionally skipped.



This allows a user with a valid token but insufficient scopes to access resources protected by scope requirements, provided they were authenticated by an earlier handler in the pipeline. The most common trigger is overlapping authentication handlers on nested routes, where a parent route authenticates broadly and a child route uses a chain to enforce specific scopes.



The impacted component Maven coordinate is io.vertx:vertx-web
Published: 2026-10-14
Score: 8.6 High
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized Resource Access
Action: Upgrade
AI Analysis

Impact

The reported vulnerability is a scope bypass flaw in Eclipse Vert.x Web's ChainAuthHandler. Because the handler does not validate authentication scopes for requests that have already been authenticated earlier in the processing pipeline, an attacker carrying a valid token that lacks the required scopes can reach endpoints that are intended to be protected by scope checks. This flaw arises from a logic error in the postAuthentication() method, which skips scope verification for pre‑authenticated users.

Affected Systems

Affected by this issue are Eclipse Vert.x Web deployments built with Vert.x releases 4.0.0 through 4.5.34, 5.0.0 through 5.0.12, 5.1.0 through 5.1.9, and the 5.2.0 release. Any application using the io.vertx:vertx-web Maven component in these ranges is vulnerable. The flaw is present when ChainAuthHandler is configured together with JWTAuthHandler or OAuth2AuthHandler that enforce scope requirements via withScope() or withScopes().

Risk and Exploitability

The reported CVSS score is 8.6, indicating high severity. The EPSS score of <1% indicates a relatively low probability of exploitation. The vulnerability is not listed in the CISA KEV catalog, so no publicly documented exploits are known. The attack is likely to occur via HTTP requests to the application, taking advantage of pre‑authenticated tokens lacking the required scopes. Because the vulnerability can be triggered by network traffic to the application and only requires a valid token, its potential impact remains significant, but the low EPSS suggests the exploitation likelihood is low to moderate in exposed deployments.

Generated by OpenCVE AI on October 19, 2026 at 16:54 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Eclipse Vert.x Web to a version that includes the ChainAuthHandler scope bypass fix – for example, Vert.x 4.5.35 or later, 5.0.13 or later, 5.1.10 or later, or 5.2.1 or later.
  • Refactor routing so that ChainAuthHandler is invoked after the initial authentication completes and that scope checks are not omitted; avoid placing broad authentication handlers on parent routes that can bypass child scope requirements.
  • If an immediate upgrade cannot be performed, restrict sensitive endpoints to use JWT or OAuth2 authentication directly, removing the ChainAuthHandler from the path, or implement a custom filter that validates scopes after authentication and before access is granted.

Generated by OpenCVE AI on October 19, 2026 at 16:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 20 Oct 2026 18:30:00 +0000

Type Values Removed Values Added
First Time appeared Eclipse
Eclipse vert.x
CPEs cpe:2.3:a:eclipse:vert.x:*:*:*:*:*:*:*:*
cpe:2.3:a:eclipse:vert.x:5.2.0:*:*:*:*:*:*:*
Vendors & Products Eclipse
Eclipse vert.x
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}

cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H'}


Mon, 19 Oct 2026 15:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-863

Sat, 17 Oct 2026 13:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

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


Sat, 17 Oct 2026 03:00:00 +0000

Type Values Removed Values Added
Weaknesses CWE-285

Sat, 17 Oct 2026 00:30:00 +0000

Type Values Removed Values Added
Title Scope Bypass in Vert.x Web ChainAuthHandler Allows Unauthorized Access io.vertx/vertx-web: vertx-web: Authorization bypass via ChainAuthHandler scope validation failure
Weaknesses CWE-425
References
Metrics threat_severity

None

cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N'}

threat_severity

Important


Thu, 15 Oct 2026 14:15:00 +0000

Type Values Removed Values Added
Title Scope Bypass in Vert.x Web ChainAuthHandler Allows Unauthorized Access
Weaknesses CWE-285

Wed, 14 Oct 2026 19:00:00 +0000

Type Values Removed Values Added
Description In Eclipse Vert.x versions [4.0.0, 4.5.34] or [5.0.0,5.0.12] or [5.1.0,5.1.9] or [5.2.0, 5.2.0], a scope bypass vulnerability exists in Eclipse Vert.x Web's ChainAuthHandler when used with scope-requiring authentication handlers such as JWTAuthHandler or OAuth2AuthHandler. When a user is already authenticated on the routing context by a preceding handler in the request pipeline, ChainAuthHandler skips all scope validation configured via withScope() or withScopes(). This affects both any() and all() chain modes. The root cause is that postAuthentication() relies on internal state that is only set during the authenticate() phase, which is skipped entirely for pre-authenticated users. In any() mode, the absence of this state causes the method to fall through without delegating scope checks to any handler. In all() mode, scope checks are unconditionally skipped. This allows a user with a valid token but insufficient scopes to access resources protected by scope requirements, provided they were authenticated by an earlier handler in the pipeline. The most common trigger is overlapping authentication handlers on nested routes, where a parent route authenticates broadly and a child route uses a chain to enforce specific scopes. The impacted component Maven coordinate is io.vertx:vertx-web
References
Metrics cvssV4_0

{'score': 8.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: eclipse

Published:

Updated: 2026-10-19T14:14:48.527Z

Reserved: 2026-09-29T08:23:57.186Z

Link: CVE-2026-102460

cve-icon Vulnrichment

Updated: 2026-10-16T18:22:26.123Z

cve-icon NVD

Status : Analyzed

Published: 2026-10-14T19:17:05.050

Modified: 2026-10-20T18:19:05.937

Link: CVE-2026-102460

cve-icon Redhat

Severity : Important

Publid Date: 2026-10-14T18:36:41Z

Links: CVE-2026-102460 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-19T17:00:18Z

Weaknesses
  • CWE-425

    Direct Request ('Forced Browsing')

  • CWE-863

    Incorrect Authorization