express vulnerabilities
Fast, unopinionated, minimalist web framework
- Registry
- npm
- Latest
- 5.3.0
- License
- MIT
5 known advisories
The latest version, 5.3.0, is not affected by any of them. Projects on older versions may be.
Update to the latest version:
npm install express@5.3.0Security advisories for express
Express ressource injection
- Affected
- <4.0.0-rc1
- Fixed in
- 4.0.0-rc1
Express Open Redirect vulnerability
- Affected
- >=3.4.5 <4.0.0-rc1
- Fixed in
- 4.0.0-rc1
express vulnerable to XSS via response.redirect()
- Affected
- <4.20.0 · >=5.0.0-alpha.1 <5.0.0
- Fixed in
- 4.20.0, 5.0.0
Express.js Open Redirect in malformed URLs
- Affected
- <4.19.2 · >=5.0.0-alpha.1 <5.0.0-beta.3
- Fixed in
- 4.19.2, 5.0.0-beta.3
No Charset in Content-Type Header in express
- Affected
- <3.11.0 · >=4.0.0 <4.5.0
- Fixed in
- 3.11.0, 4.5.0
Which of your client projects still run an old express?
NPMscan reads the package-lock.json, yarn.lock and pnpm-lock.yaml in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other npm packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the npm registry.