VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

request: vulnerability history, versions and safety

request is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, from Nov 2018 to Mar 2023. 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
1 with no fix published

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

See the unfixed vulnerabilities →
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 request vulnerabilities

Vulert verdict on request 2.88.2 i

Updated on 22 Oct 2026

Careful: 2.88.2 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 45/100
  • Security Some issues to review
  • Maintenance Deprecated
  • Popularity Key ecosystem project
  • Community Quiet

The registry marks the latest release as deprecated, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.88.2 — affected i
  • Vulnerabilities on record 2 over 4 years · 0 in the last year i
  • Latest disclosure 16 Mar 2023 i
  • Highest CVSS 6.1 i
  • With no published fix 1 i
  • Depended on by 185,822 packages i
  • Stars 25,486 i
  • OpenSSF scorecard 1/10 i
  • Last release 80 months ago i
  • Licence Apache-2.0 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 request, 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
2.88.2 11 Feb 2020 M1 Apache-2.0 No Details →
2.88.0 10 Aug 2018 M1 Apache-2.0 No Details →
2.87.0 21 May 2018 M1 Apache-2.0 No Details →
2.86.0 15 May 2018 M1 Apache-2.0 No Details →
2.85.0 12 Mar 2018 M1 Apache-2.0 No Details →
2.84.0 12 Mar 2018 M1 Apache-2.0 No Details →
2.83.0 27 Sep 2017 M1 Apache-2.0 No Details →
2.82.0 19 Sep 2017 M1 Apache-2.0 No Details →
2.81.0 09 Mar 2017 M1 Apache-2.0 No Details →
2.80.0 04 Mar 2017 M1 Apache-2.0 No Details →
2.79.0 18 Nov 2016 M1 Apache-2.0 No Details →
2.78.0 03 Nov 2016 M1 Apache-2.0 No Details →
2.77.0 03 Nov 2016 M1 Apache-2.0 No Details →
2.76.0 25 Oct 2016 M1 Apache-2.0 No Details →
2.75.0 17 Sep 2016 M1 Apache-2.0 No Details →
2.74.0 22 Jul 2016 M1 Apache-2.0 No Details →
2.73.0 09 Jul 2016 M1 Apache-2.0 No Details →
2.72.0 17 Apr 2016 M1 Apache-2.0 No Details →
2.71.0 12 Apr 2016 M1 Apache-2.0 No Details →
2.70.0 05 Apr 2016 M1 Apache-2.0 No Details →
2.69.0 27 Jan 2016 M1 Apache-2.0 No Details →
2.68.0 27 Jan 2016 M1 Apache-2.0 No Details →
2.67.0 19 Nov 2015 M2 Apache-2.0 No Details →
2.66.0 18 Nov 2015 M2 Apache-2.0 No Details →
2.65.0 11 Oct 2015 M2 Apache-2.0 No Details →
2.64.0 25 Sep 2015 M2 Apache-2.0 No Details →
2.63.0 21 Sep 2015 M2 Apache-2.0 No Details →
2.62.0 15 Sep 2015 M2 Apache-2.0 No Details →
2.61.0 19 Aug 2015 M2 Apache-2.0 No Details →
2.60.0 21 Jul 2015 M2 Apache-2.0 No Details →
2.59.0 20 Jul 2015 M2 Apache-2.0 No Details →
2.58.0 16 Jun 2015 M2 Apache-2.0 No Details →
2.57.0 31 May 2015 M2 Apache-2.0 No Details →
2.56.0 28 May 2015 M2 Apache-2.0 No Details →
2.55.0 05 Apr 2015 M2 Apache-2.0 No Details →
2.54.0 24 Mar 2015 M2 Apache-2.0 No Details →
2.53.0 02 Feb 2015 M2 Apache-2.0 No Details →
2.52.0 02 Feb 2015 M2 Apache-2.0 No Details →
2.51.0 10 Dec 2014 M2 Apache-2.0 No Details →
2.50.0 09 Dec 2014 M2 Apache-2.0 No Details →
2.49.0 28 Nov 2014 M2 Apache-2.0 No Details →
2.48.0 12 Nov 2014 M1 Apache-2.0 No Details →
2.47.0 26 Oct 2014 M1 Apache-2.0 No Details →
2.46.0 23 Oct 2014 M1 Apache-2.0 No Details →
2.45.0 06 Oct 2014 M1 Apache-2.0 No Details →
2.44.0 18 Sep 2014 M1 Apache-2.0 No Details →
2.43.0 18 Sep 2014 M1 Apache-2.0 No Details →
2.42.0 04 Sep 2014 M1 Apache-2.0 No Details →
2.41.0 04 Sep 2014 M1 Apache-2.0 No Details →
2.40.0 06 Aug 2014 M1 Apache-2.0 No Details →
2.39.0 24 Jul 2014 M1 Apache-2.0 No Details →
2.38.0 22 Jul 2014 M1 Apache-2.0 No Details →
2.37.0 07 Jul 2014 M1 Apache-2.0 No Details →
2.36.0 19 May 2014 M1 Apache-2.0 No Details →
2.35.0 17 May 2014 M1 Apache-2.0 No Details →
2.34.0 18 Feb 2014 M1 Apache-2.0 No Details →
2.33.0 16 Jan 2014 M1 Apache-2.0 No Details →
2.32.0 16 Jan 2014 M1 Apache-2.0 No Details →
2.31.0 08 Jan 2014 M1 Apache-2.0 No Details →
2.30.0 13 Dec 2013 M1 Apache-2.0 No Details →
2.29.0 06 Dec 2013 M1 Apache-2.0 No Details →
2.28.0 04 Dec 2013 M1 Apache-2.0 No Details →
2.27.0 15 Aug 2013 M1 Apache-2.0 No Details →
2.26.0 07 Aug 2013 M1 Apache-2.0 No Details →
2.25.0 23 Jul 2013 M1 Apache-2.0 No Details →
2.24.0 23 Jul 2013 M1 Apache-2.0 No Details →
2.23.0 23 Jul 2013 M1 Apache-2.0 No Details →
2.22.0 05 Jul 2013 M1 Apache-2.0 No Details →
2.21.0 30 Apr 2013 M1 Apache-2.0 No Details →
2.20.0 22 Apr 2013 M1 Apache-2.0 No Details →
2.19.0 22 Apr 2013 M1 Apache-2.0 No Details →
2.18.0 22 Apr 2013 M1 Apache-2.0 No Details →
2.16.6 18 Mar 2013 M1 Apache-2.0 No Details →
2.16.4 18 Mar 2013 M1 Apache-2.0 No Details →
2.16.2 13 Mar 2013 M1 Apache-2.0 No Details →
2.16.0 13 Mar 2013 M1 Apache-2.0 No Details →
2.14.0 19 Feb 2013 M1 Apache-2.0 No Details →
2.12.0 09 Nov 2012 M1 Apache-2.0 No Details →
2.11.4 17 Sep 2012 M1 Apache-2.0 No Details →
2.11.3 17 Sep 2012 M1 Apache-2.0 No Details →
2.11.2 17 Sep 2012 M1 Apache-2.0 No Details →
2.11.1 04 Sep 2012 M1 Apache-2.0 No Details →
2.11.0 29 Aug 2012 M1 Apache-2.0 No Details →
2.10.0 01 Aug 2012 M1 Apache-2.0 No Details →
2.9.203 28 Jun 2012 M1 Apache-2.0 No Details →
2.9.202 14 Apr 2012 M1 Apache-2.0 No Details →
2.9.201 12 Apr 2012 M1 Apache-2.0 No Details →
2.9.200 08 Apr 2012 M1 Apache-2.0 No Details →
2.9.153 01 Mar 2012 M1 Apache-2.0 No Details →
2.9.152 25 Feb 2012 M1 Apache-2.0 No Details →
2.9.151 24 Feb 2012 M1 Apache-2.0 No Details →
2.9.150 24 Feb 2012 M1 Apache-2.0 No Details →
2.9.100 20 Jan 2012 M1 Apache-2.0 No Details →
2.9.3 28 Dec 2011 M1 Apache-2.0 No Details →
2.9.2 28 Dec 2011 M1 Apache-2.0 No Details →
2.9.1 28 Dec 2011 M1 Apache-2.0 No Details →
2.9.0 28 Dec 2011 M1 Apache-2.0 No Details →
2.2.9 01 Dec 2011 M1 Apache-2.0 No Details →
2.2.6 01 Dec 2011 M1 Apache-2.0 No Details →
2.2.5 17 Nov 2011 M1 Apache-2.0 No Details →
2.2.0 06 Nov 2011 M1 — No Details →
2.1.1 23 Aug 2011 M1 — No Details →
2.1.0 15 Aug 2011 M1 — No Details →
2.0.5 13 Aug 2011 M1 — No Details →
2.0.4 13 Aug 2011 M1 — No Details →
2.0.3 12 Aug 2011 M1 — No Details →
2.0.2 29 Jul 2011 M1 — No Details →
2.0.1 21 Jul 2011 M1 — No Details →
2.0.0 21 Jul 2011 M1 — No Details →
1.9.9 21 Jul 2011 M1 — No Details →
1.9.8 23 Jun 2011 M1 — No Details →
1.9.7 23 Jun 2011 M1 — No Details →
1.9.5 27 Mar 2011 M1 — No Details →
1.9.3 22 Mar 2011 M1 — No Details →
1.9.2 22 Mar 2011 M1 — No Details →
1.9.1 22 Mar 2011 M1 — No Details →
1.9.0 11 Feb 2011 M1 — No Details →
1.2.0 30 Jan 2011 M1 — No Details →
1.1.1 23 Jan 2011 M1 — No Details →
1.1.0 23 Jan 2011 M1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2023 1

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 request

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2023-28155: Server-Side Request Forgery in Request 6.1 medium No fix published 16 Mar 2023
CVE-2017-16026: Remote Memory Exposure in request 5.9 medium 2.68.0 09 Nov 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 request

Is request safe to use?

Vulert records 2 vulnerabilities for request in npm: 0 critical, 0 high, 2 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is request's Vulert package health score?

Vulert scores request 45/100, which reads as risky. 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 registry marks the latest release as deprecated, which caps this score.

Is the latest version of request affected?

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

Which version of request should I use?

2.88.2 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 request have?

2 vulnerabilities are recorded for request in the npm 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 request vulnerabilities disclosed?

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

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