CVE-2026-73646

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% 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, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 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. Prior to 8.5.18, lib/previous-map.js loadMap() passes attacker-controlled sourceMappingURL values to join(dirname(opts.from), annotation), and loadFile() permits traversed or absolute .map paths, allowing untrusted CSS processed without map: false to disclose sourcesContent from arbitrary reachable .map files through result.map. This issue is fixed in version 8.5.18.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

July 24, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated Aug 17, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Path Traversal in Previous Source Map Auto-Loading (sourceMappingURL) leads to Arbitrary .map File Disclosure · Advisory · postcss/postcss · GitHub

https://github.com/postcss/postcss/security/advisories/GHSA-r28c-9q8g-f849
github_release Patch Available

8.5.18

Patch available: postcss/postcss 8.5.18

https://github.com/postcss/postcss/releases/tag/8.5.18
github_commit Patch Available

commit 95663d3eb7ba (postcss/postcss)

Patch available: postcss/postcss 8.5.18 (contains commit 95663d3eb7ba)

https://github.com/postcss/postcss/commit/95663d3eb7ba26f4854dd19d3b4f4425760cf56c

Vendor Advisories for CVE-2026-73646(4)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatdevspaces/openvsx-rhel9:17877591452026-09-01redhat
redhatprometheus3-5-main-3.5.5-0.8.hum12026-08-13redhat
redhatprometheus3-13-main-3.13.2-0.2.hum12026-08-04redhat

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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-postcss8.4.20+~cs8.0.23-1 ... 8.5.9+~cs9.3.30-1 (18 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-postcss8.4.49+~cs9.2.32-1 ... 8.5.9+~cs9.3.30-1 (14 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-postcss8.4.49+~cs9.2.32-1 ... 8.5.9+~cs9.3.30-1 (9 versions)8.5.19+~cs10.2.23-1—
npm(1)
PackageVulnerable rangeFixed inDependents
postcss—8.5.18—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 73× 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-09-18 20:11 UTCEG score recompute
  2. 2026-09-18 20:11 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 02:58 UTCEG score recompute
  5. 2026-09-18 02:58 UTCVendor advisory
  6. 2026-09-17 01:58 UTCEG score recompute
  7. 2026-09-17 01:58 UTCVendor advisory
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 06:39 UTCEG score recompute
  10. 2026-09-16 06:39 UTCVendor advisory
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-15 09:36 UTCEG score recompute
  13. 2026-09-15 09:36 UTCVendor advisory
  14. 2026-09-15 03:12 UTCEPSS rescore
  15. 2026-09-14 11:12 UTCVendor advisory
  16. 2026-09-13 22:14 UTCEG score recompute
  17. 2026-09-13 22:14 UTCVendor advisory
  18. 2026-09-13 07:34 UTCVendor advisory
  19. 2026-09-12 18:35 UTCEG score recompute
  20. 2026-09-12 18:35 UTCVendor advisory
  21. 2026-09-12 15:02 UTCEPSS rescore
  22. 2026-09-12 05:37 UTCVendor advisory
  23. 2026-09-11 16:36 UTCEG score recompute
  24. 2026-09-11 16:36 UTCVendor advisory
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 57 more
  1. 2026-09-11 02:37 UTCVendor advisory
  2. 2026-09-10 13:36 UTCEG score recompute
  3. 2026-09-10 13:36 UTCVendor advisory
  4. 2026-09-10 09:35 UTCEPSS rescore
  5. 2026-09-09 08:45 UTCEG score recompute
  6. 2026-09-09 08:45 UTCVendor advisory
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 21:24 UTCEG score recompute
  9. 2026-09-07 21:24 UTCVendor advisory
  10. 2026-09-06 13:48 UTCEPSS rescore
  11. 2026-09-06 08:50 UTCVendor advisory
  12. 2026-09-05 19:51 UTCEG score recompute
  13. 2026-09-05 19:51 UTCVendor advisory
  14. 2026-09-05 06:53 UTCEG score recompute
  15. 2026-09-05 06:53 UTCVendor advisory
  16. 2026-09-04 12:49 UTCEG score recompute
  17. 2026-09-04 12:49 UTCVendor advisory
  18. 2026-09-04 05:07 UTCEPSS rescore
  19. 2026-09-02 14:12 UTCEPSS rescore
  20. 2026-09-01 23:16 UTCEG score recompute
  21. 2026-09-01 23:16 UTCVendor advisory
  22. 2026-09-01 13:54 UTCEPSS rescore
  23. 2026-09-01 04:40 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-08-31 02:17 UTCEG score recompute
  26. 2026-08-31 02:17 UTCVendor advisory
  27. 2026-08-30 19:18 UTCEPSS rescore
  28. 2026-08-30 19:17 UTCEPSS rescore
  29. 2026-08-30 13:15 UTCEG score recompute
  30. 2026-08-30 13:15 UTCVendor advisory
  31. 2026-08-30 01:22 UTCEPSS rescore
  32. 2026-08-30 00:17 UTCEG score recompute
  33. 2026-08-30 00:17 UTCVendor advisory
  34. 2026-08-28 21:42 UTCEPSS rescore
  35. 2026-08-28 01:35 UTCEG score recompute
  36. 2026-08-28 01:35 UTCVendor advisory
  37. 2026-08-27 14:25 UTCEPSS rescore
  38. 2026-08-26 23:38 UTCEG score recompute
  39. 2026-08-26 14:47 UTCEPSS rescore
  40. 2026-08-25 20:47 UTCEG score recompute
  41. 2026-08-25 13:49 UTCEPSS rescore
  42. 2026-08-24 18:28 UTCEG score recompute
  43. 2026-08-23 03:32 UTCEG score recompute
  44. 2026-08-23 00:19 UTCEPSS rescore
  45. 2026-08-22 01:37 UTCEG score recompute
  46. 2026-08-21 23:49 UTCEPSS rescore
  47. 2026-08-20 23:39 UTCEG score recompute
  48. 2026-08-20 22:56 UTCEPSS rescore
  49. 2026-08-19 21:44 UTCEG score recompute
  50. 2026-08-19 17:04 UTCEPSS rescore
  51. 2026-08-18 19:26 UTCEG score recompute
  52. 2026-08-18 13:49 UTCEPSS rescore
  53. 2026-08-18 13:49 UTCEPSS rescore
  54. 2026-08-17 17:28 UTCEG score recompute
  55. 2026-08-17 16:45 UTCEG score recompute
  56. 2026-08-17 16:28 UTCEG score recompute
  57. 2026-08-13 18:52 UTCEG score recompute

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-73646?
CVE-2026-73646 is a high vulnerability published on July 24, 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. Prior to 8.5.18, lib/previous-map.js loadMap() passes attacker-controlled sourceMappingURL values to join(dirname(opts.from), annotation), and loadFile() permits…
When was CVE-2026-73646 disclosed?
CVE-2026-73646 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73646 actively exploited?
CVE-2026-73646 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 68.5% of all scored CVEs.
What is the CVSS score of CVE-2026-73646?
CVE-2026-73646 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-73646?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73646, 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-73646

Explore →

Is Your Infrastructure Affected by CVE-2026-73646?

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

Start Free Scan →Browse All CVEs