CVE-2026-45623

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — Patch released this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
9.1
EG Score
9.1(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

July 23, 2026

Last Modified

August 7, 2026

Advisory Details (1)

Auto-updated Jul 27, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Arbitrary file read and information disclosure via attacker-controlled sourceMappingURL in CSS comments · Advisory · postcss/postcss · GitHub

https://github.com/postcss/postcss/security/advisories/GHSA-6g55-p6wh-862q

Vendor Advisories for CVE-2026-45623(7)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrh-podman-desktop-0:1.1.2-1.el10_22026-08-20redhat
redhatmulticluster-engine/console-mce-rhel9:17869119772026-08-19redhat
redhatrhacm2/console-rhel9:17869083612026-08-19redhat
redhatansible-automation-platform/automation-portal:17870471882026-08-18redhat
redhatansible-automation-platform/automation-portal:17870471142026-08-18redhat
redhatrhacm2/console-rhel9:17865477712026-08-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
node-postcss8.2.1+~cs5.3.23-8 ... 8.5.9+~cs9.3.30-1 (31 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-postcss8.4.20+~cs8.0.23-1 ... 8.5.9+~cs9.3.30-1 (17 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-postcss8.4.49+~cs9.2.32-1 ... 8.5.9+~cs9.3.30-1 (13 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-postcss8.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-18.5.12+~cs9.3.32-1—
npm(1)
PackageVulnerable rangeFixed inDependents
postcss—8.5.12—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 53× in last 7d / 94× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-21 06:55 UTCVendor advisory
  2. 2026-08-21 02:46 UTCEG score recompute
  3. 2026-08-21 02:46 UTCVendor advisory
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 22:40 UTCVendor advisory
  6. 2026-08-20 18:34 UTCVendor advisory
  7. 2026-08-20 14:29 UTCVendor advisory
  8. 2026-08-20 08:51 UTCVendor advisory
  9. 2026-08-20 04:46 UTCVendor advisory
  10. 2026-08-20 00:40 UTCVendor advisory
  11. 2026-08-19 20:33 UTCEG score recompute
  12. 2026-08-19 20:33 UTCVendor advisory
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-19 16:00 UTCVendor advisory
  15. 2026-08-19 11:47 UTCVendor advisory
  16. 2026-08-19 07:41 UTCVendor advisory
  17. 2026-08-19 03:36 UTCVendor advisory
  18. 2026-08-18 23:04 UTCVendor advisory
  19. 2026-08-18 18:59 UTCEG score recompute
  20. 2026-08-18 18:59 UTCVendor advisory
  21. 2026-08-18 13:48 UTCEPSS rescore
  22. 2026-08-18 09:39 UTCVendor advisory
  23. 2026-08-18 05:34 UTCVendor advisory
  24. 2026-08-18 01:27 UTCVendor advisory
  25. 2026-08-17 20:24 UTCVendor advisory
Show 69 more
  1. 2026-08-17 14:13 UTCEG score recompute
  2. 2026-08-17 14:13 UTCVendor advisory
  3. 2026-08-17 13:47 UTCEPSS rescore
  4. 2026-08-17 10:08 UTCVendor advisory
  5. 2026-08-17 06:03 UTCVendor advisory
  6. 2026-08-17 01:54 UTCVendor advisory
  7. 2026-08-16 21:49 UTCVendor advisory
  8. 2026-08-16 17:44 UTCEG score recompute
  9. 2026-08-16 17:44 UTCVendor advisory
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 13:32 UTCVendor advisory
  12. 2026-08-16 09:27 UTCVendor advisory
  13. 2026-08-16 05:22 UTCEG score recompute
  14. 2026-08-16 05:22 UTCVendor advisory
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-16 01:17 UTCVendor advisory
  17. 2026-08-15 21:12 UTCVendor advisory
  18. 2026-08-15 17:07 UTCVendor advisory
  19. 2026-08-15 13:02 UTCVendor advisory
  20. 2026-08-15 08:57 UTCVendor advisory
  21. 2026-08-15 04:52 UTCEG score recompute
  22. 2026-08-15 04:52 UTCVendor advisory
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-15 00:46 UTCVendor advisory
  25. 2026-08-14 20:41 UTCVendor advisory
  26. 2026-08-14 16:36 UTCVendor advisory
  27. 2026-08-14 12:31 UTCVendor advisory
  28. 2026-08-14 08:25 UTCVendor advisory
  29. 2026-08-14 04:20 UTCVendor advisory
  30. 2026-08-14 00:15 UTCEG score recompute
  31. 2026-08-14 00:15 UTCVendor advisory
  32. 2026-08-13 22:00 UTCEPSS rescore
  33. 2026-08-13 20:09 UTCVendor advisory
  34. 2026-08-13 16:04 UTCVendor advisory
  35. 2026-08-12 15:31 UTCEG score recompute
  36. 2026-08-12 13:51 UTCEPSS rescore
  37. 2026-08-11 14:40 UTCEG score recompute
  38. 2026-08-11 02:23 UTCEG score recompute
  39. 2026-08-11 00:00 UTCEPSS rescore
  40. 2026-08-09 17:42 UTCEG score recompute
  41. 2026-08-09 13:46 UTCEPSS rescore
  42. 2026-08-08 17:11 UTCEG score recompute
  43. 2026-08-08 16:37 UTCEPSS rescore
  44. 2026-08-07 16:40 UTCEG score recompute
  45. 2026-08-07 00:20 UTCEG score recompute▲ 1.60
  46. 2026-08-07 00:18 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  47. 2026-08-06 15:15 UTCEG score recompute
  48. 2026-08-06 13:47 UTCEPSS rescore
  49. 2026-08-06 02:49 UTCEG score recompute
  50. 2026-08-05 19:17 UTCEPSS rescore
  51. 2026-08-05 01:09 UTCEG score recompute
  52. 2026-08-04 15:10 UTCEPSS rescore
  53. 2026-08-04 12:41 UTCEG score recompute
  54. 2026-08-04 10:38 UTCEPSS rescore
  55. 2026-08-03 11:48 UTCEG score recompute
  56. 2026-08-03 10:36 UTCEPSS rescore
  57. 2026-08-02 10:23 UTCEG score recompute
  58. 2026-08-02 02:27 UTCEPSS rescore
  59. 2026-08-01 09:32 UTCEG score recompute
  60. 2026-08-01 04:16 UTCEPSS rescore
  61. 2026-07-30 20:14 UTCEG score recompute
  62. 2026-07-30 16:28 UTCEPSS rescore
  63. 2026-07-30 08:37 UTCEG score recompute
  64. 2026-07-30 01:30 UTCEPSS rescore
  65. 2026-07-28 19:16 UTCEG score recompute
  66. 2026-07-28 15:36 UTCEPSS rescore
  67. 2026-07-27 18:22 UTCEG score recompute
  68. 2026-07-26 22:11 UTCEG score recompute
  69. 2026-07-23 15:12 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-45623?
CVE-2026-45623 is a critical vulnerability published on July 23, 2026. 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…
When was CVE-2026-45623 disclosed?
CVE-2026-45623 was first published in the National Vulnerability Database on July 23, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45623 actively exploited?
CVE-2026-45623 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.5% of all scored CVEs.
What is the CVSS score of CVE-2026-45623?
CVE-2026-45623 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-45623?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45623, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45623

Explore →

Is Your Infrastructure Affected by CVE-2026-45623?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs