CVE-2026-45623: PostCSS: Arbitrary file read and information disclosure via attacker-controlled sourceMappingURL in CSS comments
Noroxi assessment
Priority: Monitor (action score 36/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.60% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: postcss postcss 8.5.12.
Low priority for now. Upgrade to postcss postcss 8.5.12 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 27, 2026
- Updated
- Aug 6, 2026
- EPSS
- 0.6% · 49th percentile
- CWE
- CWE-22
Report tools
Action score
36
Low priority for now.
- CVSS
- 36 / 40 · 9.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.1
- CNA · GitHub_M
- 7.5
- 1.6 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| postcss | postcss | cpe:2.3:a:postcss:postcss |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
postcss postcss
- < 8.5.12affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- postcss postcssbefore 8.5.12
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | node-postcss | from 0 | — |
| Debian:14 | node-postcss | before 8.5.12+~cs9.3.32-1 | 8.5.12+~cs9.3.32-1 |
| npm | postcss | before 8.5.12 | 8.5.12 |
| openSUSE:Tumbleweed | velociraptor | before 0.76.7.0.git145.b60ef1146-1.1 | 0.76.7.0.git145.b60ef1146-1.1 |
| Red Hat:enterprise_linux:10.2 | rh-podman-desktop | before 0:1.1.2-1.el10_2 | 0:1.1.2-1.el10_2 |
Same product
postcss: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-23382Regular Expression Denial of Service (ReDoS)31Monitor
- CVE-2026-73646PostCSS: Path Traversal in Previous Source Map Auto-Loading (sourceMappingURL) leads to Arbitrary .map File Disclosure30Monitor
- CVE-2026-69153PostCSS: incomplete fix of CVE-2026-45623 — attacker-controlled sourceMappingURL reads arbitrary .map files when `from` is unset25Monitor
Published before and after this one in the same product
- ← EarlierCVE-2021-23368Apr 12, 2021 · Regular Expression Denial of Service (ReDoS)22Monitor
- ← EarlierCVE-2023-44270Sep 29, 2023 · An issue was discovered in PostCSS before 8.4.31.21Monitor
- ← EarlierCVE-2026-41305Apr 23, 2026 · PostCSS has XSS via Unescaped </style> in its CSS Stringify Output24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| postcss postcss | 8.5.12 · description | Vendor (CNA) |
| debian:node-postcss | 8.5.12+~cs9.3.32-1 · Debian:14 | Package registry (OSV) |
| npm:postcss | 8.5.12 | Package registry (OSV) |
| opensuse:velociraptor | 0.76.7.0.git145.b60ef1146-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:foreman | 0:3.18.0.14-1.el9sat · Red Hat:satellite_capsule:6.19::el9 | Package registry (OSV) |
| red hat:foreman-cli | 0:3.18.0.14-1.el9sat · Red Hat:satellite_utils:6.19::el9 | Package registry (OSV) |
| red hat:foreman-debug | 0:3.18.0.14-1.el9sat · Red Hat:satellite_capsule:6.19::el9 | Package registry (OSV) |
| red hat:foreman-dynflow-sidekiq | 0:3.18.0.14-1.el9sat · Red Hat:satellite:6.19::el9 | Package registry (OSV) |
| red hat:foreman-ec2 | 0:3.18.0.14-1.el9sat · Red Hat:satellite:6.19::el9 | Package registry (OSV) |
| red hat:foreman-journald | 0:3.18.0.14-1.el9sat · Red Hat:satellite:6.19::el9 | Package registry (OSV) |
| red hat:foreman-libvirt | 0:3.18.0.14-1.el9sat · Red Hat:satellite:6.19::el9 | Package registry (OSV) |
| red hat:foreman-openstack | 0:3.18.0.14-1.el9sat · Red Hat:satellite:6.19::el9 | Package registry (OSV) |
| red hat:foreman-pcp | 0:3.18.0.14-1.el9sat · Red Hat:satellite_capsule:6.19::el9 | Package registry (OSV) |
| red hat:rh-podman-desktop | 0:1.1.2-1.el10_2 · Red Hat:enterprise_linux:10.2 | Package registry (OSV) |
| red hat:rubygem-foreman_remote_execution | 0:16.5.3-2.el9sat · Red Hat:satellite:6.19::el9 | Package registry (OSV) |
| red hat:rubygem-foreman_remote_execution-cockpit | 0:16.5.3-2.el9sat · Red Hat:satellite:6.19::el9 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-7364621 days apartPostCSS: Path Traversal in Previous Source Map Auto-Loading (sourceMappingURL) leads to Arbitrary .map File Disclosure30Monitor
- CVE-2026-691537 days apartPostCSS: incomplete fix of CVE-2026-45623 — attacker-controlled sourceMappingURL reads arbitrary .map files when `from` is unset25Monitor
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →