Is postcss safe? Known vulnerabilities by version
postcss is a JavaScript package on npm. We track 4 of its versions: 1 of them has known vulnerabilities.
The newest stable version we track with no known advisory, as of 22 November 2026. A newer release may exist on npm.
Vulnerabilities by version
Every advisory for postcss
-
High
CVSS 7.5
CVE-2026-45623: PostCSS: Arbitrary file read and information disclosure via attacker-controlled sourceMappingURL in CSS comments
Affects 8.4.38 (of the versions we track).
-
High
CVSS 7.5
CVE-2026-73646: PostCSS: Path Traversal in Previous Source Map Auto-Loading (sourceMappingURL) leads to Arbitrary .map File Disclosure
Affects 8.4.38 (of the versions we track).
-
Medium
CVE-2026-69153: PostCSS: incomplete fix of GHSA-6g55-p6wh-862q — attacker-controlled sourceMappingURL reads arbitrary .map files when `from` is unset
Affects 8.4.38 (of the versions we track).
-
Medium
CVSS 6.1
CVE-2026-41305: PostCSS has XSS via Unescaped </style> in its CSS Stringify Output
Affects 8.4.38 (of the versions we track).
Licence
Every version we track declares MIT (from deps.dev).
Check your whole project
postcss is one package among hundreds in a lockfile. Upload your lockfile, or paste a public GitHub repository, and get every vulnerable package with the version that fixes it. Free, and no account needed.
Get emailed about new advisories for postcss (free, no account)
About this data
Vulnerability data: OSV.dev, last checked 22 November 2026. Licences: deps.dev. These pages list the versions AIssue checks every day for the projects it monitors, not every version ever released.