CVE-2026-1002: Eclipse Vert.x Web static handler file access denial

Published Jan 15, 2026
·
Updated

The Vert.x Web static handler component cache can be manipulated to deny the access to static files served by the handler using specifically crafted request URI.

The issue comes from an improper implementation of the C. rule of section 5.2.4 of RFC3986 and is fixed in Vert.x Core component (used by Vert.x Web): https://github.com/eclipse-vertx/vert.x/pull/5895

Steps to reproduce Given a file served by the static handler, craft an URI that introduces a string like bar%2F..%2F after the last / char to deny the access to the URI with an HTTP 404 response. For example https://example.com/foo/index.html can be denied with https://example.com/foo/bar%2F..%2Findex.html

Mitgation Disabling Static Handler cache fixes the issue.

StaticHandler staticHandler = StaticHandler.create().setCachingEnabled(false);

Affected Software

5 affected componentsFixes available
maven/org.eclipse/vertx-web<3.9.17
maven/io.vertx:vertx-core>=5.0.0.CR1<5.0.7
5.0.7
maven/io.vertx:vertx-core<4.5.24
4.5.24
Eclipse Vert.x-Web>=4.0.0<=4.5.23
Eclipse Vert.x-Web>=5.0.0<=5.0.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/io.vertx:vertx-core to a version that resolves this vulnerability.

    Fixed in 5.0.7
  2. Upgrade

    Upgrade maven/io.vertx:vertx-core to a version that resolves this vulnerability.

    Fixed in 4.5.24
  3. Configuration

    Disable StaticHandler cache by configuring the static handler as: StaticHandler.create().setCachingEnabled(false);

    Eclipse Vert.x Web StaticHandler cachingEnabled = false

Event History

Jan 15, 2026
CVE Published
via MITRE·08:50 PM
Data Sourced
via MITRE·08:50 PM
DescriptionWeakness
Data Sourced
via Red Hat·09:03 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·09:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·09:16 PM
RemedyAffected Software
Advisory Published
via GitHub·09:31 PM
Data Sourced
via GitHub·09:31 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-1002?

CVE-2026-1002 is classified as a medium severity vulnerability due to its potential to deny access to static files.

2

How do I fix CVE-2026-1002?

To fix CVE-2026-1002, upgrade to Vert.x Web version 5.0.7 or version 4.5.24.

3

What type of application is affected by CVE-2026-1002?

CVE-2026-1002 affects applications utilizing the Eclipse Vert.x Web static handler component.

4

Can CVE-2026-1002 allow attackers to manipulate requests?

Yes, CVE-2026-1002 allows attackers to manipulate request URIs to deny access to static files.

5

Who is responsible for patching CVE-2026-1002?

Developers using affected versions of Eclipse Vert.x must apply patches or upgrades to address CVE-2026-1002.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203