webpack vulnerabilities
Packs ECMAScript/CommonJs/AMD modules for the browser. Allows you to split your codebase into multiple bundles, which can be loaded on demand. Supports loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
- Registry
- npm
- Latest
- 5.112.2
- License
- MIT
4 known advisories
The latest version, 5.112.2, is not affected by any of them. Projects on older versions may be.
npm install webpack@5.112.2Security advisories for webpack
webpack buildHttp: allowedUris allow-list bypass via URL userinfo (@) leading to build-time SSRF behavior
- Affected
- >=5.49.0 <5.104.1
- Fixed in
- 5.104.1
webpack buildHttp HttpUriPlugin allowedUris bypass via HTTP redirects → SSRF + cache persistence
- Affected
- >=5.49.0 <5.104.0
- Fixed in
- 5.104.0
Webpack's AutoPublicPathRuntimeModule has a DOM Clobbering Gadget that leads to XSS
- Affected
- >=5.0.0-alpha.0 <5.94.0
- Fixed in
- 5.94.0
Cross-realm object access in Webpack 5
- Affected
- >=5.0.0 <5.76.0
- Fixed in
- 5.76.0
Which of your client projects still run an old webpack?
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.