Is request 2.31 vulnerable?

npm · 1 release from 2.31.0 to 2.31.0 · latest request is 2.88.2 · checked 2 Nov 2026

Yes: 2 known advisories

Yes. request 2.31.0, the last 2.31 release, is affected by 2 known security advisories (2 medium), including CVE-2023-28155, CVE-2017-16026. At least one has no fixed release yet.

Is your project affected?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Advisories affecting request 2.31.0

  • MediumCVE-2023-28155GHSA-p8p7-x288-28g616 Mar 2023

    Server-Side Request Forgery in Request

    Affected
    <=2.88.2
    Fixed in
    No fix released
  • MediumCVE-2017-16026GHSA-7xfp-9c55-5vqj9 Nov 2018

    Remote Memory Exposure in request

    Affected
    >=2.49.0 <2.68.0 · >=2.2.6 <2.68.0
    Fixed in
    2.68.0

Which of your client projects are still on request 2.31?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact request version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

Other request versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.