VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

io.quarkus:quarkus-vertx-http: vulnerability history, versions and safety

io.quarkus:quarkus-vertx-http is a package in the Maven ecosystem. Vulert records 5 vulnerabilities for it across 9 releases, from Dec 2022 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H4 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 29 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all io.quarkus:quarkus-vertx-http vulnerabilities

Vulert verdict on io.quarkus:quarkus-vertx-http 4.0.0.Beta1 i

Updated on 23 Oct 2026

Good news: 4.0.0.Beta1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

Package health score 82/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 4.0.0.Beta1 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.0.0.Beta1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.0.0.Beta1 — unaffected i
  • Vulnerabilities on record 5 over 3 years · 2 in the last year i
  • Latest disclosure 29 Jul 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Depended on by 230 packages i
  • Stars 15,951 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for io.quarkus:quarkus-vertx-http, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.40.1.1 19 Oct 2026 none Apache-2.0 — Details →
3.33.4.1 19 Oct 2026 none Apache-2.0 — Details →
3.27.6.1 19 Oct 2026 none Apache-2.0 — Details →
4.0.0.Beta1 30 Sep 2026 none Apache-2.0 — Details →
3.40.1 29 Sep 2026 none Apache-2.0 — Details →
3.40.0 23 Sep 2026 none Apache-2.0 — Details →
3.39.5 23 Sep 2026 none Apache-2.0 — Details →
3.27.6 23 Sep 2026 none Apache-2.0 — Details →
3.33.4 23 Sep 2026 none Apache-2.0 — Details →
3.27.5.3 22 Sep 2026 none Apache-2.0 — Details →
3.33.3.3 22 Sep 2026 none Apache-2.0 — Details →
3.40.0.CR1 16 Sep 2026 none Apache-2.0 — Details →
3.39.4 16 Sep 2026 none Apache-2.0 — Details →
3.39.3 09 Sep 2026 none Apache-2.0 — Details →
3.27.5.2 03 Sep 2026 none Apache-2.0 — Details →
3.33.3.2 03 Sep 2026 none Apache-2.0 — Details →
3.39.2 02 Sep 2026 none Apache-2.0 — Details →
3.39.1 26 Aug 2026 none Apache-2.0 — Details →
3.39.0 19 Aug 2026 none Apache-2.0 — Details →
3.38.3 19 Aug 2026 none Apache-2.0 — Details →
3.38.2 12 Aug 2026 none Apache-2.0 — Details →
3.39.0.CR1 12 Aug 2026 none Apache-2.0 — Details →
3.27.5.1 04 Aug 2026 none Apache-2.0 — Details →
3.33.3.1 04 Aug 2026 none Apache-2.0 — Details →
3.38.1 04 Aug 2026 none Apache-2.0 — Details →
3.33.3 23 Jul 2026 none Apache-2.0 — Details →
3.38.0 22 Jul 2026 none Apache-2.0 — Details →
3.37.4 22 Jul 2026 none Apache-2.0 — Details →
3.27.5 22 Jul 2026 none Apache-2.0 — Details →
3.38.0.CR1 15 Jul 2026 none Apache-2.0 — Details →
3.37.3 15 Jul 2026 none Apache-2.0 — Details →
3.37.2 08 Jul 2026 none Apache-2.0 — Details →
3.37.1 01 Jul 2026 none Apache-2.0 — Details →
3.37.0 17 Jun 2026 none Apache-2.0 — Details →
3.36.3 17 Jun 2026 none Apache-2.0 — Details →
3.27.4.1 17 Jun 2026 none Apache-2.0 — Details →
3.20.6.2 17 Jun 2026 none Apache-2.0 — Details →
3.33.2.1 17 Jun 2026 none Apache-2.0 — Details →
3.37.0.CR1 10 Jun 2026 none Apache-2.0 — Details →
3.36.2 10 Jun 2026 none Apache-2.0 — Details →
3.36.1 03 Jun 2026 none Apache-2.0 — Details →
3.36.0 20 May 2026 none Apache-2.0 — Details →
3.35.4 20 May 2026 none Apache-2.0 — Details →
3.33.2 20 May 2026 none Apache-2.0 — Details →
3.27.4 20 May 2026 none Apache-2.0 — Details →
3.36.0.CR1 13 May 2026 none Apache-2.0 — Details →
3.35.3 13 May 2026 none Apache-2.0 — Details →
3.34.7 04 May 2026 none Apache-2.0 — Details →
3.35.2 04 May 2026 none Apache-2.0 — Details →
3.27.3.1 04 May 2026 none Apache-2.0 — Details →
3.20.6.1 04 May 2026 H1 Apache-2.0 Yes Details →
3.33.1.1 04 May 2026 none Apache-2.0 — Details →
3.35.1 30 Apr 2026 none Apache-2.0 — Details →
3.35.0 22 Apr 2026 none Apache-2.0 — Details →
3.34.6 22 Apr 2026 none Apache-2.0 — Details →
3.35.0.CR1 16 Apr 2026 none Apache-2.0 — Details →
3.34.5 16 Apr 2026 none Apache-2.0 — Details →
3.34.4 15 Apr 2026 none Apache-2.0 — Details →
3.34.3 08 Apr 2026 none Apache-2.0 — Details →
3.34.2 01 Apr 2026 none Apache-2.0 — Details →
3.34.1 25 Mar 2026 none Apache-2.0 — Details →
3.33.1 25 Mar 2026 none Apache-2.0 — Details →
3.33.0 18 Mar 2026 none Apache-2.0 — Details →
3.32.4 18 Mar 2026 none Apache-2.0 — Details →
3.34.0 18 Mar 2026 none Apache-2.0 — Details →
3.27.3 18 Mar 2026 none Apache-2.0 — Details →
3.20.6 18 Mar 2026 H2 Apache-2.0 Yes Details →
3.34.0.CR1 12 Mar 2026 none Apache-2.0 — Details →
3.33.0.CR1 11 Mar 2026 none Apache-2.0 — Details →
3.32.3 11 Mar 2026 none Apache-2.0 — Details →
3.32.2 04 Mar 2026 none Apache-2.0 — Details →
3.32.1 25 Feb 2026 none Apache-2.0 — Details →
3.31.4 18 Feb 2026 none Apache-2.0 — Details →
3.32.0 18 Feb 2026 none Apache-2.0 — Details →
3.32.0.CR1 11 Feb 2026 none Apache-2.0 — Details →
3.31.3 11 Feb 2026 none Apache-2.0 — Details →
3.31.2 04 Feb 2026 none Apache-2.0 — Details →
3.31.1 28 Jan 2026 none Apache-2.0 — Details →
3.30.8 22 Jan 2026 none Apache-2.0 — Details →
3.31.0 21 Jan 2026 none Apache-2.0 — Details →
3.30.7 21 Jan 2026 none Apache-2.0 — Details →
3.31.0.CR1 14 Jan 2026 none Apache-2.0 — Details →
3.27.2 14 Jan 2026 none Apache-2.0 — Details →
3.20.5 14 Jan 2026 H2 Apache-2.0 Yes Details →
3.30.6 07 Jan 2026 none Apache-2.0 — Details →
3.30.5 24 Dec 2025 none Apache-2.0 — Details →
3.30.4 17 Dec 2025 none Apache-2.0 — Details →
3.30.3 10 Dec 2025 none Apache-2.0 — Details →
3.30.2 03 Dec 2025 none Apache-2.0 — Details →
3.30.1 26 Nov 2025 none Apache-2.0 — Details →
3.30.0 19 Nov 2025 none Apache-2.0 — Details →
3.29.4 19 Nov 2025 none Apache-2.0 — Details →
3.29.3 13 Nov 2025 none Apache-2.0 — Details →
3.30.0.CR1 12 Nov 2025 none Apache-2.0 — Details →
3.27.1 12 Nov 2025 none Apache-2.0 — Details →
3.20.4 12 Nov 2025 H2 Apache-2.0 Yes Details →
3.29.2 08 Nov 2025 none Apache-2.0 — Details →
3.29.1 05 Nov 2025 none Apache-2.0 — Details →
3.29.0 22 Oct 2025 none Apache-2.0 — Details →
3.28.5 22 Oct 2025 none Apache-2.0 — Details →
3.28.4 16 Oct 2025 none — — Details →
3.29.0.CR1 15 Oct 2025 none — — Details →
3.28.3 09 Oct 2025 none — — Details →
3.28.2 01 Oct 2025 none — — Details →
3.28.1 24 Sep 2025 none — — Details →
3.26.4 17 Sep 2025 none — — Details →
3.27.0 17 Sep 2025 none — — Details →
3.28.0 17 Sep 2025 none — — Details →
3.20.3 17 Sep 2025 H2 — Yes Details →
3.15.7 17 Sep 2025 H2 — Yes Details →
3.28.0.CR1 10 Sep 2025 none — — Details →
3.27.0.CR1 09 Sep 2025 none — — Details →
3.26.3 09 Sep 2025 none — — Details →
3.26.2 03 Sep 2025 none — — Details →
3.26.1 29 Aug 2025 none — — Details →
3.20.2.2 29 Aug 2025 H2 — Yes Details →
3.15.6.2 29 Aug 2025 H2 — Yes Details →
3.26.0 20 Aug 2025 none — — Details →
3.25.4 20 Aug 2025 none — — Details →
3.20.2.1 18 Aug 2025 H2 — Yes Details →

The newest 120 of 498 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2023 2
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for io.quarkus:quarkus-vertx-http

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-39852: Quarkus-Vertx-HTTP Authentication/Authorization Bypass Vulnerability 8.2 high 3.20.6.1 04 May 2026
CVE-2023-4853: Quarkus HTTP Vulnerable to Incorrect Evaluation of Permissions 8.1 high 2.16.11.Final 20 Sep 2023
CVE-2022-4147: Quarkus CORS filter allows simple GET and POST requests with an invalid Origin to proceed 7.5 high 2.14.2.Final 06 Dec 2022
CVE-2026-50559: Quarkus Vert.x HTTP Package Authentication/Authorization Bypass Vulnerability 7.5 high 3.20.6.2 29 Jul 2026
CVE-2023-0044: Cross-site Scripting in Quarkus 6.1 medium 2.13.7.Final 23 Feb 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About io.quarkus:quarkus-vertx-http

Is io.quarkus:quarkus-vertx-http safe to use?

Vulert records 5 vulnerabilities for io.quarkus:quarkus-vertx-http in Maven: 0 critical, 4 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is io.quarkus:quarkus-vertx-http's Vulert package health score?

Vulert scores io.quarkus:quarkus-vertx-http 82/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of io.quarkus:quarkus-vertx-http affected?

No. 4.0.0.Beta1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of io.quarkus:quarkus-vertx-http should I use?

4.0.0.Beta1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does io.quarkus:quarkus-vertx-http have?

5 vulnerabilities are recorded for io.quarkus:quarkus-vertx-http in the Maven ecosystem: 0 critical, 4 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new io.quarkus:quarkus-vertx-http vulnerabilities disclosed?

2 vulnerabilities were recorded for io.quarkus:quarkus-vertx-http in the last 12 months, and the oldest entry in this database dates to 06 Dec 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of io.quarkus:quarkus-vertx-http are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor io.quarkus:quarkus-vertx-http for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the io.quarkus:quarkus-vertx-http version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.