VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.ning:async-http-client: vulnerability history, versions and safety

com.ning:async-http-client is a package in the Maven ecosystem. Vulert records 2 vulnerabilities for it across 79 releases, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all com.ning:async-http-client vulnerabilities

Vulert verdict on com.ning:async-http-client 1.9.40 i

Updated on 22 Oct 2026

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

Package health score 66/100
  • Security No known security issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Inactive

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

  • Current release 1.9.40 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 13 May 2022 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 257 packages i
  • Last release 120 months ago 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 com.ning: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
1.7.24-jenkins-1 13 Feb 2024 M2 Apache-2.0 Yes Details →
1.9.40 13 Oct 2016 none Apache-2.0 — Details →
1.9.39 27 Jul 2016 none Apache-2.0 — Details →
1.9.38 03 Apr 2016 none Apache-2.0 — Details →
1.8.17 31 Mar 2016 M2 Apache-2.0 Yes Details →
1.9.37 30 Mar 2016 none Apache-2.0 — Details →
1.9.36 18 Mar 2016 none Apache-2.0 — Details →
1.9.35 16 Mar 2016 none Apache-2.0 — Details →
1.9.34 14 Mar 2016 none Apache-2.0 — Details →
1.9.33 29 Jan 2016 none Apache-2.0 — Details →
1.9.32 12 Jan 2016 none Apache-2.0 — Details →
1.9.31 30 Aug 2015 none Apache-2.0 — Details →
1.9.30 16 Jul 2015 none Apache-2.0 — Details →
1.9.29 24 Jun 2015 none Apache-2.0 — Details →
1.9.28 22 Jun 2015 none Apache-2.0 — Details →
1.9.27 12 Jun 2015 none Apache-2.0 — Details →
1.9.26 01 Jun 2015 none Apache-2.0 — Details →
1.9.25 21 May 2015 none Apache-2.0 — Details →
1.9.24 15 May 2015 none Apache-2.0 — Details →
1.9.23 15 May 2015 none Apache-2.0 — Details →
1.9.22 09 May 2015 none Apache-2.0 — Details →
1.9.21 06 May 2015 none Apache-2.0 — Details →
1.8.16 06 May 2015 M2 Apache-2.0 Yes Details →
1.9.20 17 Apr 2015 none Apache-2.0 — Details →
1.9.19 14 Apr 2015 none Apache-2.0 — Details →
1.9.18 08 Apr 2015 none Apache-2.0 — Details →
1.9.17 01 Apr 2015 none Apache-2.0 — Details →
1.9.16 30 Mar 2015 none Apache-2.0 — Details →
1.9.15 17 Mar 2015 none Apache-2.0 — Details →
1.9.14 16 Mar 2015 none Apache-2.0 — Details →
1.9.13 14 Mar 2015 none Apache-2.0 — Details →
1.9.12 10 Mar 2015 none Apache-2.0 — Details →
1.9.11 24 Feb 2015 none Apache-2.0 — Details →
1.9.10 12 Feb 2015 none Apache-2.0 — Details →
1.9.9 11 Feb 2015 none Apache-2.0 — Details →
1.9.8 27 Jan 2015 none Apache-2.0 — Details →
1.9.7 26 Jan 2015 none Apache-2.0 — Details →
1.9.6 19 Jan 2015 none Apache-2.0 — Details →
1.9.5 12 Jan 2015 none Apache-2.0 — Details →
1.9.4 08 Jan 2015 none Apache-2.0 — Details →
1.9.3 13 Dec 2014 none Apache-2.0 — Details →
1.9.2 12 Dec 2014 none Apache-2.0 — Details →
1.9.1 09 Dec 2014 none Apache-2.0 — Details →
1.9.0 01 Dec 2014 none Apache-2.0 — Details →
1.8.15 28 Nov 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA24 28 Nov 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA23 21 Nov 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA22 21 Nov 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA21 10 Nov 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA20 31 Oct 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA19 14 Oct 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA18 09 Oct 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA17 02 Oct 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA16 29 Sep 2014 M2 Apache-2.0 Yes Details →
1.8.14 23 Sep 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA15 22 Sep 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA14 18 Sep 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA13 15 Sep 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA12 09 Sep 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA11 04 Sep 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA10 27 Aug 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA9 25 Aug 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA8 25 Aug 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA7 23 Aug 2014 M2 Apache-2.0 Yes Details →
1.8.13 30 Jul 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA6 30 Jul 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA5 25 Jul 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA4 24 Jul 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA3 23 Jul 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA2 18 Jul 2014 M2 Apache-2.0 Yes Details →
1.9.0-BETA1 10 Jul 2014 M2 Apache-2.0 Yes Details →
1.8.12 01 Jul 2014 M2 Apache-2.0 Yes Details →
1.8.11 16 Jun 2014 M2 Apache-2.0 Yes Details →
1.8.10 11 Jun 2014 M2 Apache-2.0 Yes Details →
1.8.9 20 May 2014 M2 Apache-2.0 Yes Details →
1.8.8 28 Apr 2014 M2 Apache-2.0 Yes Details →
1.8.7 12 Apr 2014 M2 Apache-2.0 Yes Details →
1.8.6 09 Apr 2014 M2 Apache-2.0 Yes Details →
1.8.5 03 Apr 2014 M2 Apache-2.0 Yes Details →
1.8.4 20 Mar 2014 M2 Apache-2.0 Yes Details →
1.8.3 10 Feb 2014 M2 Apache-2.0 Yes Details →
1.8.2 07 Feb 2014 M2 Apache-2.0 Yes Details →
1.8.1 07 Feb 2014 M2 Apache-2.0 Yes Details →
1.8.0 31 Jan 2014 M2 Apache-2.0 Yes Details →
1.7.24 15 Jan 2014 M2 Apache-2.0 Yes Details →
1.7.23 18 Dec 2013 M2 Apache-2.0 Yes Details →
1.7.22 18 Dec 2013 M2 Apache-2.0 Yes Details →
1.7.21 16 Oct 2013 M2 Apache-2.0 Yes Details →
1.7.20 24 Sep 2013 M2 Apache-2.0 Yes Details →
1.7.19 30 Jul 2013 M2 Apache-2.0 Yes Details →
1.7.18 03 Jul 2013 M2 Apache-2.0 Yes Details →
1.7.17 30 May 2013 M2 Apache-2.0 Yes Details →
1.7.16 20 May 2013 M2 Apache-2.0 Yes Details →
1.7.15 03 May 2013 M2 Apache-2.0 Yes Details →
1.7.14 25 Apr 2013 M2 Apache-2.0 Yes Details →
1.7.13 12 Apr 2013 M2 Apache-2.0 Yes Details →
1.7.12 14 Mar 2013 M2 Apache-2.0 Yes Details →
1.7.11 05 Mar 2013 M2 Apache-2.0 Yes Details →
1.7.10 24 Jan 2013 M2 Apache-2.0 Yes Details →
1.7.9 19 Dec 2012 M2 Apache-2.0 Yes Details →
1.7.8 29 Nov 2012 M2 — Yes Details →
1.7.7 29 Nov 2012 M2 — Yes Details →
1.7.6 27 Aug 2012 M2 — Yes Details →
1.7.5 17 May 2012 M2 — Yes Details →
1.7.4 23 Apr 2012 M2 — Yes Details →
1.7.3 13 Apr 2012 M2 — Yes Details →
1.7.2 05 Apr 2012 M2 — Yes Details →
1.7.1 21 Feb 2012 M2 — Yes Details →
1.7.0 11 Jan 2012 M2 — Yes Details →
1.7.0-RC1 21 Dec 2011 M2 — Yes Details →
1.6.5 09 Sep 2011 M2 — Yes Details →
1.6.4 06 Jun 2011 M2 — Yes Details →
1.6.3 29 Mar 2011 M2 — Yes Details →
1.6.2 11 Mar 2011 M2 — Yes Details →
1.6.1 22 Feb 2011 M2 — Yes Details →
1.6.0 09 Feb 2011 M2 — Yes Details →
1.5.0 31 Jan 2011 M2 — Yes Details →
1.4.1 01 Dec 2010 M2 — Yes Details →
1.4.0 16 Nov 2010 M2 — Yes Details →
1.3.4 12 Nov 2010 M2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for com.ning:async-http-client

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2013-7398: Insufficient Verification of Data Authenticity in Async Http Client N/A medium 1.9.0 13 May 2022
CVE-2013-7397: Insufficient Verification of Data Authenticity in Async Http Client N/A medium 1.9.0 13 May 2022

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 com.ning:async-http-client

Is com.ning:async-http-client safe to use?

Vulert records 2 vulnerabilities for com.ning:async-http-client in Maven: 0 critical, 0 high, 2 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 com.ning:async-http-client's Vulert package health score?

Vulert scores com.ning:async-http-client 66/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 com.ning:async-http-client affected?

No. 1.9.40, 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 com.ning:async-http-client should I use?

1.9.40 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 com.ning:async-http-client have?

2 vulnerabilities are recorded for com.ning:async-http-client in the Maven ecosystem: 0 critical, 0 high, 2 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 com.ning:async-http-client vulnerabilities disclosed?

0 vulnerabilities were recorded for com.ning:async-http-client in the last 12 months, and the oldest entry in this database dates to 13 May 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 com.ning: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 com.ning:async-http-client for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the com.ning: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.