Is io.vertx:vertx-core 4.2 vulnerable?

Maven · 8 releases from 4.2.0 to 4.2.7 · latest io.vertx:vertx-core is 5.2.3 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. io.vertx:vertx-core 4.2.7, the last 4.2 release, is affected by 1 known security advisory (1 medium), including CVE-2026-1002. Upgrade to 4.5.24 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=io.vertx:vertx-core -DdepVersion=4.5.24 -DforceVersion=true

Is your project on an affected io.vertx:vertx-core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting io.vertx:vertx-core 4.2.7

  • MediumCVE-2026-1002GHSA-cphf-4846-3xx915 Jan 2026

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

    Affected
    <4.5.24 · >=5.0.0.CR1 <5.0.7
    Fixed in
    4.5.24, 5.0.7

Every io.vertx:vertx-core 4.2.x release

Affected: 4.2.0 to 4.2.7. Latest io.vertx:vertx-core: 5.2.3.

VersionKnown advisories
io.vertx:vertx-core 4.2.7CVE-2026-1002
io.vertx:vertx-core 4.2.6CVE-2026-1002
io.vertx:vertx-core 4.2.5CVE-2026-1002
io.vertx:vertx-core 4.2.4CVE-2026-1002
io.vertx:vertx-core 4.2.3CVE-2026-1002
io.vertx:vertx-core 4.2.2CVE-2026-1002
io.vertx:vertx-core 4.2.1CVE-2026-1002
io.vertx:vertx-core 4.2.0CVE-2026-1002

Which of your client projects are still on io.vertx:vertx-core 4.2?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact io.vertx:vertx-core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other io.vertx:vertx-core versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.