A security flaw has been discovered in Power Sofware PowerISO 9.3.0.0. Affected by this issue is some unknown functionality in the library C:\Windows\System32\drivers\scdemu.sys of the component Kernel Driver. The manipulation results in improper privilege management. The attack is only possible with local access. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
CVE-2026-19189
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-07. a secondary CVSS source baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- EG Risk
- 51(Track*)EG Risk 51/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 computedSeverity78% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 2%
- KEV
- Not listed
Published
August 7, 2026
Last Modified
August 12, 2026
Advisory Details (1)
Auto-updated Aug 7, 2026PowerISO 9.3.0.0 Kerne... | Winslow Blog
https://winslow1984.com/books/cve-collection/page/poweriso-9300-kernel-driver-6900-local-privilege-escalation-via-arbitrary-registry-write-or-deletionVendor Advisories for CVE-2026-19189(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 28× in last 7d / 59× 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.
- 2026-08-20 14:18 UTCGHSA enrichment
- 2026-08-20 01:42 UTCEG score recompute
- 2026-08-20 01:42 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 13:25 UTCGHSA enrichment
- 2026-08-19 01:05 UTCEG score recompute
- 2026-08-19 01:05 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 12:48 UTCGHSA enrichment
- 2026-08-17 23:49 UTCEG score recompute
- 2026-08-17 23:49 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 11:32 UTCGHSA enrichment
- 2026-08-16 23:16 UTCEG score recompute
- 2026-08-16 23:16 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 11:00 UTCEG score recompute
- 2026-08-16 11:00 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 22:44 UTCGHSA enrichment
- 2026-08-15 10:27 UTCEG score recompute
- 2026-08-15 10:27 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 22:10 UTCGHSA enrichment
- 2026-08-14 09:54 UTCEG score recompute
Show 34 moreShow fewer
- 2026-08-14 09:54 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 21:37 UTCGHSA enrichment
- 2026-08-13 09:20 UTCGHSA enrichment
- 2026-08-12 21:04 UTCGHSA enrichment
- 2026-08-12 19:06 UTCEG score recompute
- 2026-08-12 19:06 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 06:50 UTCGHSA enrichment
- 2026-08-11 18:33 UTCGHSA enrichment
- 2026-08-11 06:17 UTCEG score recompute
- 2026-08-11 06:17 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 18:01 UTCGHSA enrichment
- 2026-08-10 05:44 UTCGHSA enrichment
- 2026-08-09 17:28 UTCEG score recompute
- 2026-08-09 17:28 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 05:12 UTCGHSA enrichment
- 2026-08-08 16:56 UTCEG score recompute
- 2026-08-08 16:56 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 04:39 UTCEG score recompute
- 2026-08-08 04:39 UTCGHSA enrichment
- 2026-08-07 16:23 UTCEG score recompute
- 2026-08-07 16:23 UTCGHSA enrichment
- 2026-08-07 16:22 UTCNVD updateCVSS v4 → 7.1
- 2026-08-07 15:42 UTCMITRE cvelistV5CVSS v4 → 8.5
- 2026-08-07 15:34 UTCEG score recompute
- 2026-08-07 15:34 UTCGHSA enrichment
- 2026-08-07 03:18 UTCEG score recompute
- 2026-08-07 03:17 UTCNVD updateCVSS v4 → 7.1
- 2026-08-07 02:18 UTCEG score recompute
- 2026-08-07 02:18 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-269
Frequently asked(5)
What is CVE-2026-19189?
When was CVE-2026-19189 disclosed?
Is CVE-2026-19189 actively exploited?
What is the CVSS score of CVE-2026-19189?
How do I remediate CVE-2026-19189?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-19189
Is Your Infrastructure Affected by CVE-2026-19189?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.