VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

async: vulnerability history, versions and safety

async is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 7 releases, first recorded in Apr 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
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 async vulnerabilities

Vulert verdict on async 3.2.6 i

Updated on 22 Oct 2026

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

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

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

  • Current release 3.2.6 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 07 Apr 2022 i
  • Highest CVSS 7.8 i
  • With no published fix 0 i
  • Depended on by 190,905 packages i
  • Stars 28,117 i
  • OpenSSF scorecard 3/10 i
  • Last release 26 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, 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 async, 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.2.6 19 Aug 2024 none MIT — Details →
3.2.5 03 Nov 2023 none MIT — Details →
3.2.4 07 Jun 2022 none MIT — Details →
2.6.4 13 Apr 2022 none MIT — Details →
3.2.3 10 Jan 2022 none MIT — Details →
3.2.2 28 Oct 2021 none MIT — Details →
3.2.1 05 Aug 2021 H1 MIT Yes Details →
3.2.0 24 Feb 2020 H1 MIT Yes Details →
3.1.1 24 Jan 2020 H1 MIT Yes Details →
2.6.3 14 Jul 2019 none MIT — Details →
3.1.0 23 Jun 2019 H1 MIT Yes Details →
3.0.1 26 May 2019 H1 MIT Yes Details →
3.0.0 20 May 2019 H1 MIT Yes Details →
2.6.2 12 Feb 2019 none MIT — Details →
3.0.1-0 01 Oct 2018 H1 MIT Yes Details →
2.6.1 21 May 2018 none MIT — Details →
2.6.0 07 Nov 2017 none MIT — Details →
2.5.0 25 Jun 2017 none MIT — Details →
2.4.1 22 May 2017 none MIT — Details →
2.4.0 29 Apr 2017 none MIT — Details →
2.3.0 02 Apr 2017 none MIT — Details →
2.2.0 25 Mar 2017 none MIT — Details →
2.1.5 19 Feb 2017 none MIT — Details →
2.1.4 22 Nov 2016 none MIT — Details →
2.1.2 16 Oct 2016 none MIT — Details →
2.1.1 12 Oct 2016 none MIT — Details →
2.1.0 12 Oct 2016 none MIT — Details →
2.0.1 22 Jul 2016 none MIT — Details →
2.0.0 13 Jul 2016 none MIT — Details →
2.0.0-rc.6 07 Jun 2016 none MIT — Details →
2.0.0-rc.5 16 May 2016 none MIT — Details →
2.0.0-rc.4 05 May 2016 none MIT — Details →
2.0.0-rc.3 07 Apr 2016 none MIT — Details →
2.0.0-rc.2 24 Mar 2016 none MIT — Details →
2.0.0-rc.1 18 Mar 2016 none MIT — Details →
2.0.0-alpha.0 18 Mar 2016 none MIT — Details →
1.5.2 08 Jan 2016 none MIT — Details →
1.5.1 02 Jan 2016 none MIT — Details →
1.5.0 26 Oct 2015 none MIT — Details →
1.4.2 09 Aug 2015 none MIT — Details →
1.4.1 07 Aug 2015 none MIT — Details →
1.4.0 20 Jul 2015 none MIT — Details →
1.3.0 29 Jun 2015 none MIT — Details →
1.2.1 08 Jun 2015 none MIT — Details →
1.1.1 08 Jun 2015 none MIT — Details →
1.2.0 02 Jun 2015 none MIT — Details →
1.1.0 01 Jun 2015 none MIT — Details →
1.0.0 20 May 2015 none MIT — Details →
0.9.2 19 May 2015 none MIT — Details →
0.9.0 16 May 2014 none MIT — Details →
0.8.0 29 Apr 2014 none MIT — Details →
0.7.0 07 Apr 2014 none MIT — Details →
0.6.2 31 Mar 2014 none MIT — Details →
0.6.1 30 Mar 2014 none MIT — Details →
0.6.0 30 Mar 2014 none MIT — Details →
0.5.0 30 Mar 2014 none MIT — Details →
0.4.1 30 Mar 2014 none MIT — Details →
0.4.0 28 Mar 2014 none MIT — Details →
0.3.0 28 Mar 2014 none MIT — Details →
0.2.10 23 Jan 2014 none MIT — Details →
0.2.9 28 May 2013 none MIT — Details →
0.2.8 01 May 2013 none MIT — Details →
0.2.7 09 Apr 2013 none MIT — Details →
0.2.6 03 Mar 2013 none MIT — Details →
0.2.5 10 Feb 2013 none MIT — Details →
0.2.4 07 Feb 2013 none MIT — Details →
0.2.3 06 Feb 2013 none MIT — Details →
0.2.2 05 Feb 2013 none MIT — Details →
0.2.1 04 Feb 2013 none MIT — Details →
0.2.0 04 Feb 2013 none MIT — Details →
0.1.22 30 May 2012 none MIT — Details →
0.1.21 24 May 2012 none MIT — Details →
0.1.20 24 May 2012 none MIT — Details →
0.1.19 24 May 2012 none MIT — Details →
0.1.18 27 Feb 2012 none MIT — Details →
0.1.17 27 Feb 2012 none MIT — Details →
0.1.16 13 Feb 2012 none MIT — Details →
0.1.15 01 Nov 2011 none MIT — Details →
0.1.14 29 Oct 2011 none MIT — Details →
0.1.13 29 Oct 2011 none MIT — Details →
0.1.12 14 Oct 2011 none MIT — Details →
0.1.11 14 Oct 2011 none MIT — Details →
0.1.10 19 Sep 2011 none MIT — Details →
0.1.9 27 Apr 2011 none MIT — Details →
0.1.8 18 Jan 2011 none MIT — Details →
0.1.0 19 Dec 2010 none MIT — Details →
0.1.1 19 Dec 2010 none MIT — Details →
0.1.2 19 Dec 2010 none MIT — Details →
0.1.3 19 Dec 2010 none MIT — Details →
0.1.4 19 Dec 2010 none MIT — Details →
0.1.5 19 Dec 2010 none MIT — Details →
0.1.6 19 Dec 2010 none MIT — Details →
0.1.7 19 Dec 2010 none MIT — Details →

All 93 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for async

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-43138: Prototype Pollution in async 7.8 high 3.2.2 07 Apr 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 async

Is async safe to use?

Vulert records 1 vulnerabilities for async in npm: 0 critical, 1 high, 0 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 async's Vulert package health score?

Vulert scores async 75/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 async affected?

No. 3.2.6, 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 async should I use?

3.2.6 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 async have?

1 vulnerability is recorded for async in the npm ecosystem: 0 critical, 1 high, 0 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 async vulnerabilities disclosed?

0 vulnerabilities were recorded for async in the last 12 months, and the oldest entry in this database dates to 07 Apr 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 async 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 async for upcoming vulnerabilities?

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