NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕ Maven
Not in CISA KEV

Vert.x Web static handler component cache can be manipulated to deny the access to static filesGHSA-cphf-4846-3xx9

Fix: eclipse-vertx/vert.x#5894

GHSA-cphf-4846-3xx9 is a CWE-444 vulnerability in io.vertx:vertx-core. A fix is available for io.vertx:vertx-core — see the affected versions and patch details below.

Also known asCVE-2026-1002
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.

Exploitation and automatability from CISA’s SSVC triage for GHSA-cphf-4846-3xx9.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs33th percentile — riskier than 33% of all scored CVEsHighest risk
0.00%0.30%0.59%0.89%0.0%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected
☕io.vertx:vertx-core☕io.vertx:vertx-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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 Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.vertx:vertx-coreall versions4.5.24io.vertx:vertx-core:4.5.24
☕Mavenio.vertx:vertx-core≥ 5.0.0.CR1&&< 5.0.75.0.7io.vertx:vertx-core:5.0.7

Affected Products

1 product · 2 configurations
Application
vert.x-webeclipse
≥ 5.0.0 && ≤ 5.0.6
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.vertx:vertx-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update io.vertx:vertx-core to 4.5.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cphf-4846-3xx9 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This vulnerability allows a remote attacker to block access to specific static files, such as images, CSS or HTML files. However, the underlying Vert.x server, the API endpoints and other non-cached resources are not affected. Due to this reason, this issue has been rated with a moderate severity.

Workaround published by Red Hat
To mitigate this vulnerability, consider disabling the static handler cache by configuring the StaticHandler instance with setCachingEnabled(false), for example: ~~~ StaticHandler staticHandler = StaticHandler.create().setCachingEnabled(false); ~~~
Source: Red Hat security advisory for GHSA-cphf-4846-3xx9 (CC BY 4.0)
ProductFixed inAdvisory
Cryostat 4 on RHEL 9cryostat/cryostat-reports-rhel9:4.2.0-9RHSA-2026:17789
HawtIO HawtIO 4.4.0vertx-coreRHSA-2026:25089
Red Hat Build of Apache Camel 3.27.1.SP1io.vertx/vertx-core:4.5.22.redhat-00001RHSA-2026:8159
Red Hat build of Apache Camel 4.14.4 for Spring Boot 3.5.11vertx-coreRHSA-2026:3890
Red Hat build of Quarkus 3.20.6.redhatio.vertx/vertx-core:4.5.26.redhat-00001RHSA-2026:7109
Red Hat build of Quarkus 3.27.3.redhatio.vertx/vertx-core:4.5.26.redhat-00001RHSA-2026:7380
Red Hat JBoss EAP XP 5.0 Update 4.0vertx-coreRHSA-2026:3951
Red Hat JBoss Enterprise Application Platform 6.0.3io.vertx/vertx-core:4.5.24.redhat-00001RHSA-2026:5482

Frequently Asked Questions

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/fo
O3 Security · Impact-Aware SCA

Is GHSA-cphf-4846-3xx9 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Vert.x Web static handler component cache can be…