VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

koa: vulnerability history, versions and safety

koa is a package in the npm ecosystem. Vulert records 6 vulnerabilities for it across 117 releases, from Feb 2025 to Feb 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
6 vulnerabilities recorded C1 H1 M2 L2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 26 Feb 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all koa vulnerabilities

Vulert verdict on koa 3.2.1 i

Updated on 23 Oct 2026

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

Package health score 78/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 3.2.1 — unaffected i
  • Vulnerabilities on record 6 over 1 year · 1 in the last year i
  • Latest disclosure 26 Feb 2026 i
  • Highest CVSS 9.2 i
  • With no published fix 0 i
  • Depended on by 1,524 packages i
  • Stars 35,679 i
  • OpenSSF scorecard 4/10 i
  • Last release 5 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 koa, 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.1 21 May 2026 none MIT — Details →
3.2.0 28 Mar 2026 none MIT — Details →
2.16.4 25 Feb 2026 L1 MIT Yes Details →
3.1.2 25 Feb 2026 none MIT — Details →
3.1.1 27 Oct 2025 H1 MIT Yes Details →
3.1.0 26 Oct 2025 H1 MIT Yes Details →
2.16.3 18 Oct 2025 L1 MIT Yes Details →
3.0.3 18 Oct 2025 H1 MIT Yes Details →
3.0.2 17 Oct 2025 H1 M1 MIT Yes Details →
2.16.2 30 Jul 2025 L1 MIT Yes Details →
3.0.1 27 Jul 2025 H1 M1 MIT Yes Details →
3.0.0 28 Apr 2025 H1 L1 MIT Yes Details →
3.0.0-alpha.5 06 Apr 2025 L1 MIT Yes Details →
2.16.1 06 Apr 2025 L2 MIT Yes Details →
3.0.0-alpha.4 21 Mar 2025 L1 MIT Yes Details →
2.16.0 27 Feb 2025 M1 L2 MIT Yes Details →
3.0.0-alpha.3 11 Feb 2025 L1 MIT Yes Details →
2.15.4 11 Feb 2025 M1 L2 MIT Yes Details →
1.7.1 11 Feb 2025 M1 L1 MIT Yes Details →
0.21.2 11 Feb 2025 M1 L1 MIT Yes Details →
3.0.0-alpha.2 04 Nov 2024 L1 MIT Yes Details →
2.15.3 11 Apr 2024 C1 M1 L2 MIT Yes Details →
2.15.2 21 Mar 2024 C1 M1 L2 MIT Yes Details →
2.15.1 15 Mar 2024 C1 M1 L2 MIT Yes Details →
2.15.0 29 Dec 2023 C1 M1 L2 MIT Yes Details →
3.0.0-alpha.1 12 Apr 2023 L1 MIT Yes Details →
2.14.2 12 Apr 2023 C1 M1 L2 MIT Yes Details →
3.0.0-alpha.0 02 Jan 2023 L1 MIT Yes Details →
2.14.1 07 Dec 2022 C1 M1 L2 MIT Yes Details →
2.14.0 06 Dec 2022 C1 M1 L2 MIT Yes Details →
2.13.4 19 Oct 2021 C1 M1 L2 MIT Yes Details →
2.13.3 24 Sep 2021 C1 M1 L2 MIT Yes Details →
2.13.2 24 Sep 2021 C1 M1 L2 MIT Yes Details →
2.13.1 04 Jan 2021 C1 M1 L2 MIT Yes Details →
2.13.0 21 Jun 2020 C1 M1 L2 MIT Yes Details →
2.12.1 13 Jun 2020 C1 M1 L2 MIT Yes Details →
2.12.0 17 May 2020 C1 M1 L2 MIT Yes Details →
2.11.0 28 Oct 2019 C1 M1 L2 MIT Yes Details →
1.7.0 16 Oct 2019 M1 L1 MIT Yes Details →
2.10.0 12 Oct 2019 C1 M1 L2 MIT Yes Details →
2.9.0 12 Oct 2019 C1 M1 L2 MIT Yes Details →
2.8.2 28 Sep 2019 C1 M1 L2 MIT Yes Details →
2.8.1 19 Aug 2019 C1 M1 L2 MIT Yes Details →
2.8.0 19 Aug 2019 C1 M1 L2 MIT Yes Details →
2.7.0 28 Jan 2019 C1 M1 L2 MIT Yes Details →
2.6.2 09 Nov 2018 C1 M1 L2 MIT Yes Details →
2.6.1 23 Oct 2018 C1 M1 L2 MIT Yes Details →
2.6.0 23 Oct 2018 C1 M1 L2 MIT Yes Details →
0.21.1 12 Sep 2018 M1 L1 MIT Yes Details →
2.5.3 11 Sep 2018 C1 M1 L2 MIT Yes Details →
1.6.2 11 Sep 2018 M1 L1 MIT Yes Details →
1.6.1 11 Sep 2018 M1 L1 MIT Yes Details →
2.5.2 12 Jul 2018 C1 M1 L2 MIT Yes Details →
2.5.1 26 Apr 2018 C1 M1 L2 MIT Yes Details →
1.6.0 12 Feb 2018 M1 L1 MIT Yes Details →
2.5.0 11 Feb 2018 C1 M1 L2 MIT Yes Details →
1.5.1 25 Jan 2018 M1 L1 MIT Yes Details →
1.5.0 24 Jan 2018 M1 L1 MIT Yes Details →
2.4.1 06 Nov 2017 C1 M1 L2 MIT Yes Details →
1.4.1 09 Oct 2017 M1 L1 MIT Yes Details →
2.3.0 20 Jun 2017 C1 M1 L2 MIT Yes Details →
1.4.0 20 Mar 2017 M1 L1 MIT Yes Details →
2.2.0 14 Mar 2017 C1 M1 L2 MIT Yes Details →
1.3.0 08 Mar 2017 M1 L1 MIT Yes Details →
2.1.0 08 Mar 2017 C1 M1 L2 MIT Yes Details →
2.0.1 25 Feb 2017 C1 M1 L2 MIT Yes Details →
2.0.0-alpha.8 13 Feb 2017 M1 L1 MIT Yes Details →
1.2.5 11 Feb 2017 M1 L1 MIT Yes Details →
2.0.0-alpha.7 07 Sep 2016 M1 L1 MIT Yes Details →
1.2.4 07 Sep 2016 M1 L1 MIT Yes Details →
1.2.3 07 Sep 2016 M1 L1 MIT Yes Details →
1.2.2 31 Aug 2016 M1 L1 MIT Yes Details →
2.0.0-alpha.6 29 Aug 2016 M1 L1 MIT Yes Details →
2.0.0-alpha.5 10 Aug 2016 M1 L1 MIT Yes Details →
2.0.0-alpha.4 23 Jul 2016 M1 L1 MIT Yes Details →
1.2.1 22 Jul 2016 M1 L1 MIT Yes Details →
2.0.0 23 Mar 2016 C1 M1 L2 MIT Yes Details →
1.2.0 04 Mar 2016 M1 L1 MIT Yes Details →
1.1.2 05 Nov 2015 M1 L1 MIT Yes Details →
2.0.0-alpha.3 05 Nov 2015 M1 L1 MIT Yes Details →
2.0.0-alpha.2 27 Oct 2015 M1 L1 MIT Yes Details →
1.1.1 22 Oct 2015 M1 L1 MIT Yes Details →
2.0.0-alpha.1 22 Oct 2015 M1 L1 MIT Yes Details →
1.1.0 11 Oct 2015 M1 L1 MIT Yes Details →
1.0.0 22 Aug 2015 M1 L1 MIT Yes Details →
0.21.0 24 May 2015 M1 L1 MIT Yes Details →
0.20.0 30 Apr 2015 M1 L1 MIT Yes Details →
0.19.1 14 Apr 2015 M1 L1 MIT Yes Details →
0.19.0 05 Apr 2015 M1 L1 MIT Yes Details →
0.18.1 01 Mar 2015 M1 L1 MIT Yes Details →
0.18.0 15 Feb 2015 M1 L1 MIT Yes Details →
0.17.0 06 Feb 2015 M1 L1 MIT Yes Details →
0.16.0 27 Jan 2015 M1 L1 MIT Yes Details →
0.15.0 19 Jan 2015 M1 L1 MIT Yes Details →
0.14.0 15 Dec 2014 M1 L1 MIT Yes Details →
0.13.0 18 Oct 2014 M1 L1 MIT Yes Details →
0.12.2 29 Sep 2014 M1 L1 MIT Yes Details →
0.12.1 22 Sep 2014 M1 L1 MIT Yes Details →
0.12.0 20 Sep 2014 M1 L1 MIT Yes Details →
0.11.0 08 Sep 2014 M1 L1 MIT Yes Details →
0.10.0 12 Aug 2014 M1 L1 — Yes Details →
0.9.0 08 Aug 2014 M1 L1 — Yes Details →
0.8.2 28 Jul 2014 M1 L1 — Yes Details →
0.8.1 25 Jun 2014 M1 L1 — Yes Details →
0.8.0 13 Jun 2014 M1 L1 — Yes Details →
0.7.0 07 Jun 2014 M1 L1 — Yes Details →
0.6.3 06 Jun 2014 M1 L1 — Yes Details →
0.6.2 04 Jun 2014 M1 L1 — Yes Details →
0.6.1 12 May 2014 M1 L1 — Yes Details →
0.6.0 02 May 2014 M1 L1 — Yes Details →
0.5.5 14 Apr 2014 M1 L1 — Yes Details →
0.5.4 12 Apr 2014 M1 L1 — Yes Details →
0.5.3 09 Apr 2014 M1 L1 — Yes Details →
0.5.2 23 Mar 2014 M1 L1 — Yes Details →
0.5.1 07 Mar 2014 M1 L1 — Yes Details →
0.5.0 20 Feb 2014 M1 L1 — Yes Details →
0.4.0 11 Feb 2014 M1 L1 — Yes Details →
0.3.0 18 Jan 2014 M1 L1 — Yes Details →
0.2.1 30 Dec 2013 M1 L1 — Yes Details →
0.2.0 29 Dec 2013 M1 L1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 5
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for koa

The 5 most severe of 6 vulnerabilities recorded for this package

Search all 6 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-25200: Koa Package Suffers from Regex Denial-of-Service Vulnerability 9.2 critical 2.15.4 12 Feb 2025
CVE-2026-27959: Koa Host Header Injection Vulnerability 7.5 high 3.1.2 26 Feb 2026
CVE-2025-32379: Koa Package Vulnerable to Cross-Site Scripting (XSS) via ctx.redirect() Function 5.0 medium 2.16.1 09 Apr 2025
CVE-2025-62595: Koa Vulnerable to Open Redirect via Trailing Double-Slash in Back Redirect Logic 4.7 medium 3.0.3 21 Oct 2025
CVE-2025-8129: Koa Open Redirect Vulnerability in KoaJS 3.5 low 3.0.1 25 Jul 2025

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 koa

Is koa safe to use?

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

Vulert scores koa 78/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 koa affected?

No. 3.2.1, 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 koa should I use?

3.2.1 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 koa have?

6 vulnerabilities are recorded for koa in the npm ecosystem: 1 critical, 1 high, 2 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 koa vulnerabilities disclosed?

1 vulnerability was recorded for koa in the last 12 months, and the oldest entry in this database dates to 12 Feb 2025. 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 koa 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 koa for upcoming vulnerabilities?

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