CVE-2026-69153

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 76% 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 weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: 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.19, if from is unset, an attacker can cause PreviousMap.loadFile() to read an unintended source-map file by supplying an absolute or directory-traversal sourceMappingURL. The resulting map’s sources and sourcesContent may then be exposed to the application. This issue is fixed in version 8.5.19.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity53% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 5, 2026

Advisory Details (3)

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

8.5.19

Patch available: postcss/postcss 8.5.19

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

commit 7beca139e70f (postcss/postcss)

Patch available: postcss/postcss 8.5.23 (contains commit 7beca139e70f)

https://github.com/postcss/postcss/commit/7beca139e70f9075c6b19700fcb00dd8033e5da8
github Patch Available🟡 PoC Available

PostCSS: incomplete fix of GHSA-6g55-p6wh-862q — attacker-controlled sourceMappingURL reads arbitrary .map files when `from` is unset · Advisory · postcss/postcss · GitHub

https://github.com/postcss/postcss/security/advisories/GHSA-fxqj-rqcc-2cmp

Vendor Advisories for CVE-2026-69153(9)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatdiscovery/discovery-ui-rhel9:17866348252026-08-13redhat
redhatpostcss2026-08-12redhat
redhatgrafana13-1-main-13.1.1-0.5.2.hum12026-08-05redhat
redhatprometheus3-5-main-3.5.5-0.7.hum12026-08-04redhat
redhatgrafana12-4-main-12.4.6-0.4.hum12026-08-04redhat
redhatgrafana13-1-main-13.1.1-0.5.1.hum12026-08-04redhat
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

(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.9+~cs9.3.30-1 (11 versions)8.5.23+~cs10.2.23-1—
npm(1)
PackageVulnerable rangeFixed inDependents
postcss—8.5.23—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 38× 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-15 05:08 UTCEG score recompute
  2. 2026-08-15 05:08 UTCVendor advisory
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 06:08 UTCEG score recompute
  5. 2026-08-14 06:08 UTCVendor advisory
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 07:09 UTCEG score recompute
  8. 2026-08-13 07:09 UTCVendor advisory
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-12 08:02 UTCEG score recompute
  11. 2026-08-12 08:02 UTCVendor advisory
  12. 2026-08-11 09:03 UTCEG score recompute
  13. 2026-08-11 09:03 UTCVendor advisory
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-10 10:03 UTCEG score recompute
  16. 2026-08-10 10:03 UTCVendor advisory
  17. 2026-08-09 13:47 UTCEPSS rescore
  18. 2026-08-09 11:04 UTCEG score recompute
  19. 2026-08-09 11:04 UTCVendor advisory
  20. 2026-08-08 16:37 UTCEPSS rescore
  21. 2026-08-08 12:05 UTCEG score recompute
  22. 2026-08-08 12:05 UTCVendor advisory
  23. 2026-08-07 13:05 UTCVendor advisory
  24. 2026-08-06 14:06 UTCEG score recompute
  25. 2026-08-06 14:06 UTCVendor advisory
Show 13 more
  1. 2026-08-06 13:47 UTCEPSS rescore
  2. 2026-08-05 19:17 UTCEPSS rescore
  3. 2026-08-05 19:17 UTCEPSS rescore
  4. 2026-08-05 15:06 UTCEG score recompute▼ 1.00
  5. 2026-08-05 15:06 UTCVendor advisory
  6. 2026-08-05 15:06 UTCNVD updateCVSS v3 → 5.3
  7. 2026-08-04 18:17 UTCEG score recompute
  8. 2026-08-04 15:10 UTCEPSS rescore
  9. 2026-08-03 19:18 UTCEG score recompute
  10. 2026-08-03 19:05 UTCEG score recompute
  11. 2026-08-03 17:38 UTCEG score recompute
  12. 2026-08-03 17:09 UTCEG score recompute
  13. 2026-08-03 17:08 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-69153?
CVE-2026-69153 is a medium vulnerability published on August 3, 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.19, if from is unset, an attacker can cause PreviousMap.loadFile() to read an unintended source-map file by supplying an absolute or directory-traversal…
When was CVE-2026-69153 disclosed?
CVE-2026-69153 was first published in the National Vulnerability Database on August 3, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-69153 actively exploited?
CVE-2026-69153 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 76.1% of all scored CVEs.
What is the CVSS score of CVE-2026-69153?
CVE-2026-69153 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-69153?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69153, 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-69153

Explore →

Is Your Infrastructure Affected by CVE-2026-69153?

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

Start Free Scan →Browse All CVEs