postcss vulnerabilities
Tool for transforming styles with JS plugins
- Registry
- npm
- Latest
- 8.5.31
- License
- MIT
7 known advisories
The latest version, 8.5.31, is not affected by any of them. Projects on older versions may be.
npm install postcss@8.5.31Security advisories for postcss
PostCSS: incomplete fix of GHSA-6g55-p6wh-862q — attacker-controlled sourceMappingURL reads arbitrary .map files when `from` is unset
- Affected
- <8.5.23
- Fixed in
- 8.5.23
PostCSS: Path Traversal in Previous Source Map Auto-Loading (sourceMappingURL) leads to Arbitrary .map File Disclosure
- Affected
- <8.5.18
- Fixed in
- 8.5.18
PostCSS: Arbitrary file read and information disclosure via attacker-controlled sourceMappingURL in CSS comments
- Affected
- <8.5.12
- Fixed in
- 8.5.12
PostCSS has XSS via Unescaped </style> in its CSS Stringify Output
- Affected
- <8.5.10
- Fixed in
- 8.5.10
PostCSS line return parsing error
- Affected
- <8.4.31
- Fixed in
- 8.4.31
Regular Expression Denial of Service in postcss
- Affected
- >=8.0.0 <8.2.13 · <7.0.36
- Fixed in
- 7.0.36, 8.2.13
Regular Expression Denial of Service in postcss
- Affected
- >=7.0.0 <7.0.36 · >=8.0.0 <8.2.10
- Fixed in
- 7.0.36, 8.2.10
Which of your client projects still run an old postcss?
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.