Vert.x Web static handler component cache can be manipulated to deny the access to static files

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L · score source

EPSS

• CVE-2026-1002: 0.38% estimated exploitation activity in the next 30 days; percentile 32.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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);

Published by the source

15 Jan 2026, 21:31 UTC

Last modified by the source

16 Jan 2026, 20:20 UTC

Source last checked

26 Oct 2026, 16:43 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cphf-4846-3xx9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-1002

Advisory: Vert.x Web static handler component cache can be manipulated to deny the access to static files
IDs: CVE-2026-1002, GHSA-cphf-4846-3xx9
Record: https://patchnext.com/advisories/cve-2026-1002 (revision 1, source checked 26 Oct 2026, 16:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: io.vertx:vertx-core 5.0.7, 4.5.24. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.vertx:vertx-core: affected < 4.5.24; >= 5.0.0.CR1, < 5.0.7; fixed in 4.5.24, 5.0.7

## Suggested inspection (read-only)
- Maven io.vertx:vertx-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.vertx:vertx-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cphf-4846-3xx9 (GitHub-reviewed advisory GHSA-cphf-4846-3xx9 lists affected ranges: Maven io.vertx:vertx-core >=0 =5.0.0.CR1 <5.0.7)

Commands are suggestions: review each one before running it.