VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

superagent: vulnerability history, versions and safety

superagent is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 52 releases, first recorded in Aug 2018. 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 M1
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 superagent vulnerabilities

Vulert verdict on superagent 10.4.1 i

Updated on 22 Oct 2026

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

Package health score 97/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

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

  • Current release 10.4.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 09 Aug 2018 i
  • Highest CVSS 5.9 i
  • With no published fix 0 i
  • Depended on by 1,425 packages i
  • Stars 16,629 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 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 superagent, 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
10.4.1 23 Sep 2026 none MIT — Details →
10.4.0 22 Sep 2026 none MIT — Details →
10.3.0 06 Jan 2026 none MIT — Details →
10.2.3 22 Jul 2025 none MIT — Details →
10.2.2 07 Jul 2025 none MIT — Details →
10.2.1 05 May 2025 none MIT — Details →
10.2.0 11 Mar 2025 none MIT — Details →
10.1.1 18 Oct 2024 none MIT — Details →
10.1.0 24 Aug 2024 none MIT — Details →
10.0.2 15 Aug 2024 none MIT — Details →
10.0.1 13 Aug 2024 none MIT — Details →
10.0.0 05 Aug 2024 none MIT — Details →
9.0.2 29 Apr 2024 none MIT — Details →
9.0.1 23 Apr 2024 none MIT — Details →
9.0.0 23 Apr 2024 none MIT — Details →
8.1.2 15 Aug 2023 none MIT — Details →
8.1.1 15 Aug 2023 none MIT — Details →
8.1.0 15 Aug 2023 none MIT — Details →
8.0.9 25 Jan 2023 none MIT — Details →
8.0.8 18 Jan 2023 none MIT — Details →
8.0.7 18 Jan 2023 none MIT — Details →
8.0.6 07 Dec 2022 none MIT — Details →
8.0.5 02 Dec 2022 none MIT — Details →
8.0.4 25 Nov 2022 none MIT — Details →
8.0.3 24 Oct 2022 none MIT — Details →
8.0.2 03 Oct 2022 none MIT — Details →
8.0.1 29 Sep 2022 none MIT — Details →
8.0.0 24 Jun 2022 none MIT — Details →
7.1.6 01 Jun 2022 none MIT — Details →
7.1.5 01 Jun 2022 none MIT — Details →
7.1.4 31 May 2022 none MIT — Details →
7.1.3 26 Apr 2022 none MIT — Details →
7.1.2 29 Mar 2022 none MIT — Details →
7.1.1 19 Jan 2022 none MIT — Details →
7.1.0 18 Jan 2022 none MIT — Details →
7.0.2 11 Jan 2022 none MIT — Details →
7.0.1 07 Jan 2022 none MIT — Details →
7.0.0 07 Jan 2022 none MIT — Details →
6.1.0 30 Aug 2020 none MIT — Details →
6.0.0 08 Aug 2020 none MIT — Details →
5.3.1 28 Jun 2020 none MIT — Details →
5.3.0 28 Jun 2020 none MIT — Details →
5.2.2 17 Feb 2020 none MIT — Details →
5.2.1 07 Jan 2020 none MIT — Details →
5.2.0 07 Jan 2020 none MIT — Details →
5.1.4 07 Jan 2020 none MIT — Details →
5.1.3 20 Dec 2019 none MIT — Details →
5.1.2 01 Dec 2019 none MIT — Details →
5.1.1 21 Nov 2019 none MIT — Details →
5.1.0 15 Jun 2019 none MIT — Details →
5.0.9 14 Jun 2019 none MIT — Details →
5.0.8 12 Jun 2019 none MIT — Details →
5.0.6 06 Jun 2019 none MIT — Details →
5.0.5 29 Apr 2019 none MIT — Details →
5.0.4 28 Apr 2019 none MIT — Details →
5.0.3 25 Apr 2019 none MIT — Details →
5.0.2 28 Mar 2019 none MIT — Details →
4.1.0 26 Dec 2018 none MIT — Details →
4.1.0-beta.1 02 Dec 2018 none MIT — Details →
4.0.0 17 Nov 2018 none MIT — Details →
4.0.0-beta.5 17 Sep 2018 none MIT — Details →
4.0.0-alpha.1 29 Apr 2018 none MIT — Details →
3.8.3 29 Apr 2018 none MIT — Details →
3.8.2 09 Dec 2017 none MIT — Details →
3.8.1 08 Nov 2017 none MIT — Details →
3.8.0 25 Oct 2017 none MIT — Details →
3.8.0-alpha.1 21 Oct 2017 none MIT — Details →
3.7.0 19 Oct 2017 none MIT — Details →
3.6.3 04 Oct 2017 M1 MIT Yes Details →
3.6.2 02 Oct 2017 M1 MIT Yes Details →
3.6.1 28 Sep 2017 M1 MIT Yes Details →
3.6.0 20 Aug 2017 M1 MIT Yes Details →
3.5.3-beta.2 30 Mar 2017 M1 MIT Yes Details →
3.5.3-beta.1 29 Mar 2017 M1 MIT Yes Details →
3.5.2 22 Mar 2017 M1 MIT Yes Details →
3.5.1 18 Mar 2017 M1 MIT Yes Details →
3.5.0 23 Feb 2017 M1 MIT Yes Details →
3.4.4 17 Feb 2017 M1 MIT Yes Details →
3.4.3 14 Feb 2017 M1 MIT Yes Details →
3.4.2 03 Feb 2017 M1 MIT Yes Details →
3.4.1 29 Jan 2017 M1 MIT Yes Details →
3.4.0 25 Jan 2017 M1 MIT Yes Details →
3.3.2 11 Jan 2017 M1 MIT Yes Details →
3.3.1 17 Dec 2016 M1 MIT Yes Details →
3.3.0 14 Dec 2016 M1 MIT Yes Details →
3.2.1 11 Dec 2016 M1 MIT Yes Details →
3.2.0 11 Dec 2016 M1 MIT Yes Details →
1.8.5 11 Dec 2016 M1 MIT Yes Details →
3.1.0 28 Nov 2016 M1 MIT Yes Details →
3.0.0 19 Nov 2016 M1 MIT Yes Details →
3.0.0-alpha.3 15 Nov 2016 M1 MIT Yes Details →
3.0.0-alpha.2 08 Nov 2016 M1 MIT Yes Details →
3.0.0-alpha.1 30 Oct 2016 M1 MIT Yes Details →
2.3.0 20 Sep 2016 M1 MIT Yes Details →
2.2.0 13 Aug 2016 M1 MIT Yes Details →
1.8.4 12 Aug 2016 M1 MIT Yes Details →
2.1.0 14 Jul 2016 M1 MIT Yes Details →
2.1.0-beta.1 11 Jun 2016 M1 MIT Yes Details →
2.0.0 29 May 2016 M1 MIT Yes Details →
2.0.0-alpha.3 18 May 2016 M1 MIT Yes Details →
2.0.0-alpha.2 30 Apr 2016 M1 — Yes Details →
2.0.0-alpha.1 26 Mar 2016 M1 — Yes Details →
1.8.3 24 Mar 2016 M1 — Yes Details →
1.8.2 21 Mar 2016 M1 — Yes Details →
1.8.1 14 Mar 2016 M1 — Yes Details →
1.8.0 09 Mar 2016 M1 — Yes Details →
1.8.0-beta.2 27 Feb 2016 M1 — Yes Details →
1.8.0-beta.1 25 Feb 2016 M1 — Yes Details →
1.7.2 26 Jan 2016 M1 — Yes Details →
1.7.1 21 Jan 2016 M1 — Yes Details →
1.7.0 19 Jan 2016 M1 — Yes Details →
1.6.1 16 Dec 2015 M1 — Yes Details →
1.6.0 16 Dec 2015 M1 — Yes Details →
1.5.0 03 Dec 2015 M1 — Yes Details →
1.4.0 15 Sep 2015 M1 — Yes Details →
1.3.0 05 Aug 2015 M1 — Yes Details →
1.2.0 13 Apr 2015 M1 — Yes Details →
1.1.0 13 Mar 2015 M1 — Yes Details →
1.0.0 11 Mar 2015 M1 — Yes Details →
0.21.0 11 Nov 2014 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 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 superagent

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-16129: Large gzip Denial of Service in superagent 5.9 medium 3.7.0 09 Aug 2018

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 superagent

Is superagent safe to use?

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

Vulert scores superagent 97/100, which reads as healthy. 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 superagent affected?

No. 10.4.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 superagent should I use?

10.4.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 superagent have?

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

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

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