VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.asynchttpclient:async-http-client: vulnerability history, versions and safety

org.asynchttpclient:async-http-client is a package in the Maven ecosystem. Vulert records 18 vulnerabilities for it across 119 releases, from Oct 2018 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
18 vulnerabilities recorded C2 H6 M8 L2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
16 in the last 12 months

Most recent disclosure 08 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.asynchttpclient:async-http-client vulnerabilities

Vulert verdict on org.asynchttpclient:async-http-client 3.0.14 i

Updated on 23 Oct 2026

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

Package health score 62/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 3.0.14 — unaffected i
  • Vulnerabilities on record 18 over 7 years · 16 in the last year i
  • Latest disclosure 08 Oct 2026 i
  • Highest CVSS 9.4 i
  • With no published fix 0 i
  • Depended on by 30 packages i
  • Stars 6,396 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 22 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 org.asynchttpclient:async-http-client, 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.0.14 24 Sep 2026 none Apache-2.0 — Details →
2.16.1 09 Aug 2026 M1 Apache-2.0 Yes Details →
3.0.13 09 Aug 2026 H2 M2 Apache-2.0 Yes Details →
3.0.12 09 Aug 2026 C1 H3 M3 Apache-2.0 Yes Details →
2.16.0 15 Jun 2026 M1 Apache-2.0 Yes Details →
3.0.11 14 Jun 2026 C1 H4 M6 L2 Apache-2.0 Yes Details →
3.0.10 12 May 2026 C1 H4 M7 L2 Apache-2.0 Yes Details →
2.15.0 12 May 2026 M1 Apache-2.0 Yes Details →
2.14.5 16 Apr 2026 M1 Apache-2.0 Yes Details →
3.0.9 12 Apr 2026 C1 H5 M7 L2 Apache-2.0 Yes Details →
3.0.8 28 Mar 2026 C1 H5 M7 L2 Apache-2.0 Yes Details →
3.0.7 11 Feb 2026 C1 H5 M7 L1 Apache-2.0 Yes Details →
3.0.6 31 Dec 2025 C1 H5 M7 L1 Apache-2.0 Yes Details →
3.0.5 18 Dec 2025 C1 H5 M7 L1 Apache-2.0 Yes Details →
3.0.4 14 Nov 2025 C1 H5 M7 L1 Apache-2.0 Yes Details →
3.0.3 07 Sep 2025 C1 H5 M7 L1 Apache-2.0 Yes Details →
3.0.2 31 Mar 2025 C1 H5 M7 L1 Apache-2.0 Yes Details →
2.12.4 15 Dec 2024 M1 Apache-2.0 Yes Details →
3.0.1 02 Dec 2024 C1 H5 M7 L1 Apache-2.0 Yes Details →
3.0.0 29 Jul 2024 C1 H5 M7 L1 Apache-2.0 Yes Details →
3.0.0.Beta3 03 Nov 2023 H2 M2 Apache-2.0 Yes Details →
3.0.0.Beta2 24 Apr 2023 H2 M2 Apache-2.0 Yes Details →
3.0.0.Beta1 17 Jan 2023 H2 M2 Apache-2.0 Yes Details →
2.12.3 27 Mar 2021 C1 M1 Apache-2.0 Yes Details →
2.12.2 02 Jan 2021 C1 M1 Apache-2.0 Yes Details →
2.12.1 08 Apr 2020 C1 M1 Apache-2.0 Yes Details →
2.12.0 03 Apr 2020 C1 M1 Apache-2.0 Yes Details →
2.11.0 04 Mar 2020 C1 M1 Apache-2.0 Yes Details →
2.10.5 07 Feb 2020 C1 M1 Apache-2.0 Yes Details →
2.0.40 14 Oct 2019 M1 Apache-2.0 Yes Details →
2.10.4 12 Oct 2019 C1 M1 Apache-2.0 Yes Details →
2.10.3 27 Sep 2019 C1 M1 Apache-2.0 Yes Details →
2.10.2 05 Sep 2019 C1 M1 Apache-2.0 Yes Details →
2.10.1 25 Jun 2019 C1 M1 Apache-2.0 Yes Details →
2.10.0 03 Jun 2019 C1 M1 Apache-2.0 Yes Details →
2.9.0 21 May 2019 C1 M1 Apache-2.0 Yes Details →
2.8.1 28 Feb 2019 C1 M1 Apache-2.0 Yes Details →
2.8.0 27 Feb 2019 C1 M1 Apache-2.0 Yes Details →
2.7.0 24 Jan 2019 C1 M1 Apache-2.0 Yes Details →
2.6.0 29 Oct 2018 C1 M1 Apache-2.0 Yes Details →
2.5.4 05 Oct 2018 C1 M1 Apache-2.0 Yes Details →
2.5.3 04 Sep 2018 C1 M1 Apache-2.0 Yes Details →
2.5.2 12 Jul 2018 C1 M1 Apache-2.0 Yes Details →
2.5.1 11 Jul 2018 C1 M1 Apache-2.0 Yes Details →
2.5.0 11 Jul 2018 C1 M1 Apache-2.0 Yes Details →
2.4.9 04 Jun 2018 C1 M1 Apache-2.0 Yes Details →
2.4.8 29 May 2018 C1 M1 Apache-2.0 Yes Details →
2.4.7 29 Apr 2018 C1 M1 Apache-2.0 Yes Details →
2.4.6 29 Apr 2018 C1 M1 Apache-2.0 Yes Details →
2.4.5 06 Apr 2018 C1 M1 Apache-2.0 Yes Details →
2.4.4 08 Mar 2018 C1 M1 Apache-2.0 Yes Details →
2.0.39 27 Feb 2018 M1 Apache-2.0 Yes Details →
2.4.3 27 Feb 2018 C1 M1 Apache-2.0 Yes Details →
2.4.2 21 Feb 2018 C1 M1 Apache-2.0 Yes Details →
2.4.1 16 Feb 2018 C1 M1 Apache-2.0 Yes Details →
2.4.0 12 Feb 2018 C1 M1 Apache-2.0 Yes Details →
2.3.0 05 Feb 2018 C1 M1 Apache-2.0 Yes Details →
2.2.1 29 Jan 2018 C1 M1 Apache-2.0 Yes Details →
2.2.0 22 Jan 2018 C1 M1 Apache-2.0 Yes Details →
2.1.2 18 Jan 2018 C1 M1 Apache-2.0 Yes Details →
2.1.1 18 Jan 2018 C1 M1 Apache-2.0 Yes Details →
2.1.0 15 Jan 2018 C1 M1 Apache-2.0 Yes Details →
2.1.0-RC4 11 Jan 2018 M1 Apache-2.0 Yes Details →
2.1.0-RC3 20 Dec 2017 M1 Apache-2.0 Yes Details →
2.1.0-RC2 13 Dec 2017 M1 Apache-2.0 Yes Details →
2.0.38 13 Dec 2017 M1 Apache-2.0 Yes Details →
2.1.0-RC1 30 Nov 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha26 10 Nov 2017 M1 Apache-2.0 Yes Details →
2.0.37 25 Sep 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha25 25 Sep 2017 M1 Apache-2.0 Yes Details →
2.0.36 15 Sep 2017 M1 Apache-2.0 Yes Details →
2.0.35 28 Aug 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha24 28 Aug 2017 M1 Apache-2.0 Yes Details →
2.0.34 04 Aug 2017 H1 M1 Apache-2.0 Yes Details →
2.1.0-alpha23 04 Aug 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha22 31 Jul 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha21 07 Jul 2017 M1 Apache-2.0 Yes Details →
2.0.33 28 Jun 2017 H1 M1 Apache-2.0 Yes Details →
2.1.0-alpha20 09 Jun 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha19 19 May 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha18 12 May 2017 M1 Apache-2.0 Yes Details →
2.0.32 01 May 2017 H1 M1 Apache-2.0 Yes Details →
2.1.0-alpha17 01 May 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha16 28 Apr 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha15 28 Apr 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha14 25 Apr 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha13 25 Apr 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha12 19 Apr 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha11 31 Mar 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha10 30 Mar 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha9 28 Mar 2017 M1 Apache-2.0 Yes Details →
2.0.31 27 Mar 2017 H1 M1 Apache-2.0 Yes Details →
2.1.0-alpha8 14 Mar 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha7 12 Mar 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha6 08 Mar 2017 M1 Apache-2.0 Yes Details →
2.0.30 06 Mar 2017 H1 M1 Apache-2.0 Yes Details →
2.1.0-alpha5 17 Feb 2017 M1 Apache-2.0 Yes Details →
2.0.29 15 Feb 2017 H1 M1 Apache-2.0 Yes Details →
2.1.0-alpha4 08 Feb 2017 M1 Apache-2.0 Yes Details →
2.1.0-alpha3 07 Feb 2017 M1 Apache-2.0 Yes Details →
2.0.28 02 Feb 2017 H1 M1 — Yes Details →
2.0.27 26 Jan 2017 H1 M1 — Yes Details →
2.0.26 15 Jan 2017 H1 M1 — Yes Details →
2.1.0-alpha2 12 Jan 2017 M1 — Yes Details →
2.0.25 12 Jan 2017 H1 M1 — Yes Details →
2.0.24 08 Nov 2016 H1 M1 — Yes Details →
2.0.23 07 Nov 2016 H1 M1 — Yes Details →
2.0.22 07 Nov 2016 H1 M1 — Yes Details →
2.0.21 29 Oct 2016 H1 M1 — Yes Details →
2.0.20 27 Oct 2016 H1 M1 — Yes Details →
2.0.19 17 Oct 2016 H1 M1 — Yes Details →
2.0.18 15 Oct 2016 H1 M1 — Yes Details →
2.0.17 14 Oct 2016 H1 M1 — Yes Details →
2.0.16 05 Oct 2016 H1 M1 — Yes Details →
2.0.15 10 Sep 2016 H1 M1 — Yes Details →
2.0.14 26 Aug 2016 H1 M1 — Yes Details →
2.0.13 26 Aug 2016 H1 M1 — Yes Details →
2.0.12 16 Aug 2016 H1 M1 — Yes Details →
2.1.0-alpha1 10 Aug 2016 M1 — Yes Details →
2.0.11 21 Jul 2016 H1 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2024 1
  • 2026 16

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

03 Vulnerabilities

Recorded vulnerabilities for org.asynchttpclient:async-http-client

The 5 most severe of 18 vulnerabilities recorded for this package

Search all 18 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-107282: AsyncHttpClient Replay Vulnerability Exposing Credentials to Different Hosts 9.4 critical 3.0.13 08 Oct 2026
CVE-2024-53990: AsyncHttpClient CookieStore Vulnerability Leading to User Cookie Overwrites 9.2 critical 2.12.4 02 Dec 2024
CVE-2026-107231: AsyncHttpClient Digest Challenge Vulnerability Leading to Basic Authentication Exposure 8.7 high 3.0.13 08 Oct 2026
CVE-2017-14063: Improper Input Validation in async-http-client 7.5 high 2.0.35 19 Oct 2018
CVE-2026-107227: AsyncHttpClient Unbounded WebSocket Compression Vulnerability 7.5 high 3.0.14 08 Oct 2026

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 org.asynchttpclient:async-http-client

Is org.asynchttpclient:async-http-client safe to use?

Vulert records 18 vulnerabilities for org.asynchttpclient:async-http-client in Maven: 2 critical, 6 high, 8 medium and 2 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 org.asynchttpclient:async-http-client's Vulert package health score?

Vulert scores org.asynchttpclient:async-http-client 62/100, which reads as usable, but worth attention. 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 org.asynchttpclient:async-http-client affected?

No. 3.0.14, 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 org.asynchttpclient:async-http-client should I use?

3.0.14 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 org.asynchttpclient:async-http-client have?

18 vulnerabilities are recorded for org.asynchttpclient:async-http-client in the Maven ecosystem: 2 critical, 6 high, 8 medium and 2 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.asynchttpclient:async-http-client vulnerabilities disclosed?

16 vulnerabilities were recorded for org.asynchttpclient:async-http-client in the last 12 months, and the oldest entry in this database dates to 19 Oct 2018. 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 org.asynchttpclient:async-http-client 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 org.asynchttpclient:async-http-client for upcoming vulnerabilities?

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