p PatchFirst

CVE-2026-45623

CVE-2026-45623 · PostCSS: Arbitrary file read and information disclosure via attacker-controlled sourceMappingURL in CSS comments

This page contains facts from public vulnerability sources. Check the original advisory before updating.

PostCSS takes a CSS file and provides an API to analyze and modify its rules by transforming the rules into an Abstract Syntax Tree. In versions 8.5.11 and prior, the PreviousMap parses the /*# sourceMappingURL=PATH */ comment from any CSS string passed to process() and dereferences PATH against the local filesystem with no scheme, allowlist, or traversal check. An attacker who controls the CSS input can cause the host process to read any file readable by Node and leak the first ~10 bytes of its content through the resulting JSON.parse SyntaxError message. The bug also yields a precise file-existence oracle and a controllable-read primitive that may be combined with large-file targets for DoS. The behaviour is triggered with PostCSS's default options — no from, no map, no plugins required — and is therefore reachable from any pipeline that runs untrusted CSS through PostCSS (CMS themes, user-uploaded styles, browser-extension/userstyle processors, build pipelines for third-party packages, blog comment renderers, etc.). This issue has been fixed in version 8.5.12.

CVSS 7.5 · High · EPSS 0.6% · Fix available

Published
Updated

Stack: system · node

Affected products and versions

  • postcss

    Versions
    • < 8.5.12: Affected

    No fix published

  • node-postcss Debian:12

    Versions
    • 8.4.20+~cs8.0.23-1
    • 8.4.20+~cs8.0.23-1+deb12u1
    • 8.4.31+~cs8.0.26-1
    • 8.4.39+~cs9.2.29-1
    • 8.4.49+~cs9.2.32-1
    • 8.5.12+~cs9.3.32-1
    • 8.5.14+~cs9.3.34-1
    • 8.5.15+~cs9.3.34-1
    • 8.5.15+~cs9.3.38-1
    • 8.5.15+~cs9.3.39-1
    • 8.5.19+~cs10.2.23-1
    • 8.5.21+~cs10.2.23-1
    • 8.5.23+~cs10.2.23-1
    • 8.5.25+~cs10.2.23-1
    • 8.5.26+~cs10.2.24-1
    • 8.5.28+~cs10.2.24-1
    • 8.5.6+~cs9.3.28-1
    • 8.5.8+~cs9.3.30-1
    • 8.5.9+~cs9.3.30-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-postcss Debian:13

    Versions
    • 8.4.49+~cs9.2.32-1
    • 8.5.12+~cs9.3.32-1
    • 8.5.14+~cs9.3.34-1
    • 8.5.15+~cs9.3.34-1
    • 8.5.15+~cs9.3.38-1
    • 8.5.15+~cs9.3.39-1
    • 8.5.19+~cs10.2.23-1
    • 8.5.21+~cs10.2.23-1
    • 8.5.23+~cs10.2.23-1
    • 8.5.25+~cs10.2.23-1
    • 8.5.26+~cs10.2.24-1
    • 8.5.28+~cs10.2.24-1
    • 8.5.6+~cs9.3.28-1
    • 8.5.8+~cs9.3.30-1
    • 8.5.9+~cs9.3.30-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-postcss Debian:14

    Versions
    • 8.4.49+~cs9.2.32-1
    • 8.5.6+~cs9.3.28-1
    • 8.5.8+~cs9.3.30-1
    • 8.5.9+~cs9.3.30-1
    Affected ranges
    • ECOSYSTEM: < 8.5.12+~cs9.3.32-1

    Update to 8.5.12+~cs9.3.32-1

  • postcss npm

    Affected ranges
    • SEMVER: < 8.5.12

    Update to 8.5.12

  • node-postcss Ubuntu:20.04:LTS

    Versions
    • 6.0.23-1
    • 6.0.23-3
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-postcss Ubuntu:22.04:LTS

    Versions
    • 8.2.1+~cs5.3.23-8
    • 8.4.5+~cs7.1.51-2
    • 8.4.6+~cs7.3.21-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-postcss Ubuntu:24.04:LTS

    Versions
    • 8.4.20+~cs8.0.23-1
    • 8.4.31+~cs8.0.26-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-postcss Ubuntu:26.10

    Versions
    • 8.5.8+~cs9.3.30-1
    • 8.5.15+~cs9.3.34-1
    • 8.5.15+~cs9.3.38-1
    • 8.5.15+~cs9.3.39-1build1
    • 8.5.25+~cs10.2.23-1
    • 8.5.26+~cs10.2.24-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

  • node-postcss Ubuntu:26.04:LTS

    Versions
    • 8.5.6+~cs9.3.28-1
    • 8.5.8+~cs9.3.30-1
    Affected ranges
    • ECOSYSTEM: (−∞, +∞)

    No fix published

Original sources

Check your server →