CVE-2026-19190

HIGHPre-NVD 7.87.8
EchelonGraph scoreHIGH confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
7.8EG
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.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A weakness has been identified in StableBit Scanner 2.6.13.4088. This affects an unknown part of the file C:\Program Files (x86)\StableBit\Scanner\Service\Scanner.Service.exe of the component ScannerService. This manipulation causes permission issues. The attack is restricted to local execution. The exploit has been made available to the public and could be used for attacks.

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 computed
Severity78% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

August 7, 2026

Last Modified

August 12, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-19190(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 29× in last 7d / 63× 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-20 10:20 UTCGHSA enrichment
  2. 2026-08-19 23:01 UTCEG score recompute
  3. 2026-08-19 23:01 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 11:40 UTCGHSA enrichment
  6. 2026-08-19 00:20 UTCEG score recompute
  7. 2026-08-19 00:20 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 13:00 UTCGHSA enrichment
  10. 2026-08-18 01:40 UTCGHSA enrichment
  11. 2026-08-17 14:20 UTCEG score recompute
  12. 2026-08-17 14:20 UTCGHSA enrichment
  13. 2026-08-17 13:47 UTCEPSS rescore
  14. 2026-08-17 03:01 UTCGHSA enrichment
  15. 2026-08-16 15:41 UTCEG score recompute
  16. 2026-08-16 15:41 UTCGHSA enrichment
  17. 2026-08-16 14:56 UTCEPSS rescore
  18. 2026-08-16 04:21 UTCEG score recompute
  19. 2026-08-16 04:21 UTCGHSA enrichment
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-15 17:02 UTCGHSA enrichment
  22. 2026-08-15 05:42 UTCEG score recompute
  23. 2026-08-15 05:42 UTCGHSA enrichment
  24. 2026-08-15 01:30 UTCEPSS rescore
  25. 2026-08-14 18:22 UTCGHSA enrichment
Show 38 more
  1. 2026-08-14 07:03 UTCEG score recompute
  2. 2026-08-14 07:03 UTCGHSA enrichment
  3. 2026-08-13 22:00 UTCEPSS rescore
  4. 2026-08-13 19:43 UTCGHSA enrichment
  5. 2026-08-13 08:24 UTCGHSA enrichment
  6. 2026-08-12 21:05 UTCEG score recompute
  7. 2026-08-12 21:04 UTCGHSA enrichment
  8. 2026-08-12 13:50 UTCEPSS rescore
  9. 2026-08-12 11:42 UTCGHSA enrichment
  10. 2026-08-12 00:22 UTCEG score recompute
  11. 2026-08-12 00:22 UTCGHSA enrichment
  12. 2026-08-11 13:42 UTCEPSS rescore
  13. 2026-08-11 13:02 UTCGHSA enrichment
  14. 2026-08-11 01:43 UTCEG score recompute
  15. 2026-08-11 01:43 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 14:23 UTCGHSA enrichment
  18. 2026-08-10 03:04 UTCGHSA enrichment
  19. 2026-08-09 15:44 UTCEG score recompute
  20. 2026-08-09 15:44 UTCGHSA enrichment
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-09 04:25 UTCGHSA enrichment
  23. 2026-08-08 17:06 UTCEG score recompute
  24. 2026-08-08 17:06 UTCGHSA enrichment
  25. 2026-08-08 16:37 UTCEPSS rescore
  26. 2026-08-08 05:46 UTCGHSA enrichment
  27. 2026-08-07 18:27 UTCEG score recompute
  28. 2026-08-07 18:27 UTCGHSA enrichment
  29. 2026-08-07 18:26 UTCNVD updateCVSS v4 → 7.1
  30. 2026-08-07 18:07 UTCEG score recompute
  31. 2026-08-07 18:07 UTCGHSA enrichment
  32. 2026-08-07 18:07 UTCMITRE cvelistV5CVSS v4 → 8.5
  33. 2026-08-07 15:37 UTCEG score recompute
  34. 2026-08-07 15:37 UTCGHSA enrichment
  35. 2026-08-07 04:18 UTCEG score recompute
  36. 2026-08-07 04:18 UTCNVD updateCVSS v4 → 7.1
  37. 2026-08-07 03:23 UTCEG score recompute
  38. 2026-08-07 03:23 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-19190?
CVE-2026-19190 is a high vulnerability published on August 7, 2026. A weakness has been identified in StableBit Scanner 2.6.13.4088. This affects an unknown part of the file C:\Program Files (x86)\StableBit\Scanner\Service\Scanner.Service.exe of the component ScannerService. This manipulation causes permission issues. The attack is restricted to local execution.…
When was CVE-2026-19190 disclosed?
CVE-2026-19190 was first published in the National Vulnerability Database on August 7, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19190 actively exploited?
CVE-2026-19190 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 96.4% of all scored CVEs.
What is the CVSS score of CVE-2026-19190?
CVE-2026-19190 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-19190?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19190, 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

Explore the affected products and dependency analysis for CVE-2026-19190

Explore →

Is Your Infrastructure Affected by CVE-2026-19190?

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