VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

axios: vulnerability history, versions and safety

axios is a package in the npm ecosystem. Vulert records 68 vulnerabilities for it across 120 releases, from May 2019 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
68 vulnerabilities recorded C3 H28 M35 L2
i
11 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
59 in the last 12 months

Most recent disclosure 30 Sep 2026.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all axios vulnerabilities

Vulert verdict on axios 1.20.0 i

Updated on 22 Oct 2026

Careful: 1.20.0 was published with malicious code in it, not just a bug. Do not install it.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

The current release contains malicious code, which caps this score.

What to do: Do not resolve 1.20.0 as-is. Check whether you already run an affected release and pin a version the maintainers have re-published. Check what you run: Vulert alerts you when a safe version is published. Monitor it with Vulert →

  • Current release 1.20.0 — affected i
  • Vulnerabilities on record 68 over 7 years · 59 in the last year i
  • Latest disclosure 30 Sep 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 11 i
  • Malicious packages 1 i
  • Depended on by 173,091 packages i
  • Stars 109,302 i
  • OpenSSF scorecard 7/10 i
  • Last release 1 month 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 axios, 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
0.34.0 16 Sep 2026 C3 H3 M2 malicious MIT No Details →
1.20.0 26 Aug 2026 C1 H1 M9 malicious MIT No Details →
1.19.0 29 Jul 2026 C1 H7 M13 malicious MIT No Details →
1.18.1 22 Jun 2026 C1 H7 M13 malicious MIT No Details →
1.18.0 14 Jun 2026 C1 H7 M13 malicious MIT No Details →
0.33.0 14 Jun 2026 C3 H4 M3 malicious MIT No Details →
1.17.0 03 Jun 2026 C1 H7 M18 malicious MIT No Details →
1.16.1 13 May 2026 C1 H6 M18 malicious MIT No Details →
0.32.0 04 May 2026 C3 H5 M7 malicious MIT No Details →
1.16.0 02 May 2026 C1 H5 M18 malicious MIT No Details →
1.15.2 21 Apr 2026 L1 MIT Yes Details →
0.31.1 19 Apr 2026 C3 H5 M7 malicious MIT No Details →
1.15.1 19 Apr 2026 C1 H11 M18 malicious MIT No Details →
0.31.0 12 Apr 2026 C3 H4 M6 malicious MIT No Details →
1.15.0 08 Apr 2026 C1 H14 M24 L1 malicious MIT No Details →
1.14.0 27 Mar 2026 C3 H13 M22 L1 malicious MIT No Details →
1.13.6 27 Feb 2026 C3 H13 M22 L1 malicious MIT No Details →
0.30.3 18 Feb 2026 C3 H4 M6 malicious MIT No Details →
1.13.5 08 Feb 2026 C3 H13 M22 L1 malicious MIT No Details →
1.13.4 27 Jan 2026 C3 H14 M22 L1 malicious MIT No Details →
1.13.3 25 Jan 2026 C3 H14 M22 L1 malicious MIT No Details →
1.13.2 04 Nov 2025 C3 H14 M22 L1 malicious MIT No Details →
1.13.1 28 Oct 2025 C3 H14 M23 L1 malicious MIT No Details →
1.13.0 27 Oct 2025 C3 H14 M23 L1 malicious MIT No Details →
0.30.2 27 Sep 2025 C3 H4 M6 malicious MIT No Details →
1.12.2 14 Sep 2025 C3 H12 M21 L1 malicious MIT No Details →
1.12.1 12 Sep 2025 C3 H12 M21 L1 malicious MIT No Details →
1.12.0 11 Sep 2025 C3 H12 M21 L1 malicious MIT No Details →
0.30.1 04 Aug 2025 C3 H4 M6 malicious MIT No Details →
1.11.0 23 Jul 2025 C3 H14 M20 L1 malicious MIT No Details →
1.10.0 14 Jun 2025 H1 MIT Yes Details →
1.9.0 24 Apr 2025 C3 H14 M20 L1 malicious MIT No Details →
0.30.0 26 Mar 2025 C3 H4 M6 malicious MIT No Details →
1.8.4 19 Mar 2025 C3 H14 M20 L1 malicious MIT No Details →
1.8.3 12 Mar 2025 C3 H14 M20 L1 malicious MIT No Details →
1.8.2 07 Mar 2025 C3 H14 M20 L1 malicious MIT No Details →
1.8.1 26 Feb 2025 C3 H15 M20 L1 malicious MIT No Details →
1.8.0 26 Feb 2025 C3 H15 M20 L1 malicious MIT No Details →
1.7.9 04 Dec 2024 C3 H15 M20 L1 malicious MIT No Details →
1.7.8 25 Nov 2024 C3 H15 M20 L1 malicious MIT No Details →
0.29.0 21 Nov 2024 C3 H4 M6 malicious MIT No Details →
1.7.7 31 Aug 2024 C3 H15 M20 L1 malicious MIT No Details →
1.7.6 30 Aug 2024 C3 H15 M20 L1 malicious MIT No Details →
1.7.5 23 Aug 2024 C3 H15 M20 L1 malicious MIT No Details →
1.7.4 13 Aug 2024 C3 H15 M20 L1 malicious MIT No Details →
1.7.3 01 Aug 2024 C3 H16 M20 L1 malicious MIT No Details →
1.7.2 21 May 2024 C3 H16 M20 L1 malicious MIT No Details →
1.7.1 20 May 2024 C3 H16 M20 L1 malicious MIT No Details →
1.7.0 19 May 2024 C3 H16 M20 L1 malicious MIT No Details →
1.7.0-beta.2 19 May 2024 C3 H15 M17 L1 malicious MIT No Details →
1.7.0-beta.1 07 May 2024 C3 H15 M17 L1 malicious MIT No Details →
1.7.0-beta.0 28 Apr 2024 C3 H15 M17 L1 malicious MIT No Details →
0.28.1 28 Mar 2024 C3 H4 M6 malicious MIT No Details →
1.6.8 15 Mar 2024 C3 H15 M17 L1 malicious MIT No Details →
0.28.0 12 Feb 2024 C3 H4 M6 malicious MIT No Details →
1.6.7 25 Jan 2024 C3 H15 M17 L1 malicious MIT No Details →
1.6.6 24 Jan 2024 C3 H15 M17 L1 malicious MIT No Details →
1.6.5 05 Jan 2024 C3 H15 M17 L1 malicious MIT No Details →
1.6.4 03 Jan 2024 C3 H15 M17 L1 malicious MIT No Details →
1.6.3 26 Dec 2023 C3 H15 M17 L1 malicious MIT No Details →
1.6.2 14 Nov 2023 C3 H15 M17 L1 malicious MIT No Details →
1.6.1 08 Nov 2023 C3 H15 M17 L1 malicious MIT No Details →
1.6.0 26 Oct 2023 C3 H15 M17 L1 malicious MIT No Details →
1.5.1 26 Sep 2023 C3 H15 M18 L1 malicious MIT No Details →
1.5.0 26 Aug 2023 C3 H15 M18 L1 malicious MIT No Details →
1.4.0 27 Apr 2023 C3 H15 M18 L1 malicious MIT No Details →
1.3.6 19 Apr 2023 C3 H15 M18 L1 malicious MIT No Details →
1.3.5 05 Apr 2023 C3 H15 M18 L1 malicious MIT No Details →
1.3.4 22 Feb 2023 C3 H15 M18 L1 malicious MIT No Details →
1.3.3 13 Feb 2023 C3 H15 M18 L1 malicious MIT No Details →
1.3.2 03 Feb 2023 C3 H15 M18 L1 malicious MIT No Details →
1.3.1 01 Feb 2023 C3 H14 M18 L1 malicious MIT No Details →
1.3.0 31 Jan 2023 C3 H14 M18 L1 malicious MIT No Details →
1.2.6 28 Jan 2023 C3 H14 M18 L1 malicious MIT No Details →
1.2.5 26 Jan 2023 C3 H14 M18 L1 malicious MIT No Details →
1.2.4 24 Jan 2023 C3 H14 M18 L1 malicious MIT No Details →
1.2.3 17 Jan 2023 C3 H14 M18 L1 malicious MIT No Details →
1.2.2 29 Dec 2022 C3 H14 M18 L1 malicious MIT No Details →
1.2.1 05 Dec 2022 C3 H14 M18 L1 malicious MIT No Details →
1.2.0 22 Nov 2022 C3 H14 M18 L1 malicious MIT No Details →
1.2.0-alpha.1 10 Nov 2022 C3 H14 M18 L1 malicious MIT No Details →
1.1.3 15 Oct 2022 C3 H14 M18 L1 malicious MIT No Details →
1.1.2 07 Oct 2022 C3 H14 M18 L1 malicious MIT No Details →
1.1.1 07 Oct 2022 C3 H14 M18 L1 malicious MIT No Details →
1.1.0 06 Oct 2022 C3 H14 M18 L1 malicious MIT No Details →
1.0.0 04 Oct 2022 C3 H14 M18 L1 malicious MIT No Details →
1.0.0-alpha.1 31 May 2022 C3 H3 M2 malicious MIT No Details →
0.27.2 27 Apr 2022 C3 H3 M4 malicious MIT No Details →
0.27.1 26 Apr 2022 C3 H3 M3 malicious MIT No Details →
0.27.0 25 Apr 2022 C3 H3 M3 malicious MIT No Details →
0.26.1 09 Mar 2022 C3 H3 M3 malicious MIT No Details →
0.26.0 13 Feb 2022 C3 H3 M3 malicious MIT No Details →
0.25.0 18 Jan 2022 C3 H3 M3 malicious MIT No Details →
0.24.0 25 Oct 2021 C3 H3 M3 malicious MIT No Details →
0.23.0 12 Oct 2021 C3 H3 M3 malicious MIT No Details →
0.22.0 01 Oct 2021 C3 H3 M3 malicious MIT No Details →
0.21.4 06 Sep 2021 C3 H3 M3 malicious MIT No Details →
0.21.3 04 Sep 2021 C3 H3 M3 malicious MIT No Details →
0.21.2 04 Sep 2021 C3 H3 M3 malicious MIT No Details →
0.21.1 22 Dec 2020 C3 H4 M3 malicious MIT No Details →
0.21.0 23 Oct 2020 C3 H4 M4 malicious — No Details →
0.20.0 21 Aug 2020 C3 H4 M4 malicious — No Details →
0.20.0-0 15 Jul 2020 C3 H4 M4 malicious — No Details →
0.19.2 22 Jan 2020 C3 H4 M4 malicious — No Details →
0.19.1 07 Jan 2020 C3 H4 M4 malicious — No Details →
0.18.1 01 Jun 2019 C3 H4 M4 malicious — No Details →
0.19.0 30 May 2019 C3 H4 M4 malicious — No Details →
0.19.0-beta.1 09 Aug 2018 C3 H4 M4 malicious — No Details →
0.18.0 19 Feb 2018 C3 H5 M4 malicious — No Details →
0.17.1 11 Nov 2017 C3 H5 M4 malicious — No Details →
0.17.0 21 Oct 2017 C3 H5 M4 malicious — No Details →
0.16.2 03 Jun 2017 C3 H5 M4 malicious — No Details →
0.16.1 08 Apr 2017 C3 H5 M4 malicious — No Details →
0.16.0 01 Apr 2017 C3 H5 M4 malicious — No Details →
0.15.3 27 Nov 2016 C3 H5 M4 malicious — No Details →
0.15.2 18 Oct 2016 C3 H5 M4 malicious — No Details →
0.15.1 15 Oct 2016 C3 H5 M4 malicious — No Details →
0.15.0 11 Oct 2016 C3 H5 M4 malicious — No Details →
0.14.0 27 Aug 2016 C3 H5 M4 malicious — No Details →
0.13.1 16 Jul 2016 C3 H5 M4 malicious — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2021 2
  • 2023 1
  • 2024 1
  • 2025 4
  • 2026 59

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

03 Vulnerabilities

Recorded vulnerabilities for axios

The 5 most severe of 68 vulnerabilities recorded for this package

Search all 68 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-40175: Axios Library Vulnerability Leading to Unrestricted Cloud Metadata Exfiltration 10.0 critical 1.15.0 10 Apr 2026
CVE-2025-62718: Axios NO_PROXY Hostname Normalization Bypass Leading to SSRF 9.3 critical 1.15.0 09 Apr 2026
CVE-2026-44494: axios Prototype Pollution Vulnerability Leading to Full Man-in-the-Middle Attack 8.7 high 1.16.0 29 May 2026
CVE-2026-44492: axios NO_PROXY Bypass via IPv4-Mapped IPv6 Addresses 8.6 high 1.16.0 29 May 2026
CVE-2026-101909: Axios Prototype Pollution Vulnerability in toFormData Options 8.3 high 0.34.0 30 Sep 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: 22/Oct/2026 · Vulnerabilities in our DB: 524167

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 →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Add Vulert as a Preferred Source

Questions

About axios

Is axios safe to use?

Vulert records 68 vulnerabilities for axios in npm: 3 critical, 28 high, 35 medium and 2 low. 11 of them have no published fix yet, so those are the ones to avoid or mitigate. 1 are malicious-package vulnerabilities: the published package itself contained hostile code, not only a bug.

What is axios's Vulert package health score?

Vulert scores axios 15/100, which reads as critical. 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). The current release contains malicious code, which caps this score.

Is the latest version of axios affected?

Yes. 1.20.0, the version you would install today, has 11 known vulnerabilities, and 11 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of axios should I use?

1.20.0 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 axios have?

68 vulnerabilities are recorded for axios in the npm ecosystem: 3 critical, 28 high, 35 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 axios vulnerabilities disclosed?

59 vulnerabilities were recorded for axios in the last 12 months, and the oldest entry in this database dates to 29 May 2019. 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 axios 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.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor axios for upcoming vulnerabilities?

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