CVE-2026-19139

HIGHPre-NVD 7.47.4—
EchelonGraph scoreHIGH confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-08-07. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this week
7.4EG
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.4Exploit: None knownExposed: 0

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

Race in CredentialProvider in Google Chrome on Windows prior to 151.0.7922.109 allowed a local attacker to perform OS-level privilege escalation via a malicious file. (Chromium security severity: High)

CVSS v3
7.4
Vendor severity
HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
EG Score
7.4(high)
EG Risk
33(Track)
EG Risk 33/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
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

August 6, 2026

Last Modified

August 7, 2026

Advisory Details (2)

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

Chromium

https://issues.chromium.org/issues/511731805
generic

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_01193673229.html

Vendor Advisories for CVE-2026-19139(2)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
chromium100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (503 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
chromium113.0.5672.126-1 ... 151.0.7922.71-1~deb13u1 (400 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb13u1 (163 versions)151.0.7922.108-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 151.0.7922.71-1~deb13u1 (165 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 34× in last 7d / 69× 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 03:19 UTCEG score recompute
  2. 2026-08-21 03:19 UTCVendor advisory
  3. 2026-08-21 03:19 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 14:18 UTCVendor advisory
  6. 2026-08-20 14:18 UTCGHSA enrichment
  7. 2026-08-20 01:13 UTCEG score recompute
  8. 2026-08-20 01:13 UTCGHSA enrichment
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-19 12:13 UTCVendor advisory
  11. 2026-08-19 12:13 UTCGHSA enrichment
  12. 2026-08-18 23:13 UTCEG score recompute
  13. 2026-08-18 23:13 UTCGHSA enrichment
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-18 10:13 UTCVendor advisory
  16. 2026-08-18 10:13 UTCGHSA enrichment
  17. 2026-08-17 21:13 UTCEG score recompute
  18. 2026-08-17 21:13 UTCVendor advisory
  19. 2026-08-17 21:13 UTCGHSA enrichment
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-17 08:13 UTCVendor advisory
  22. 2026-08-17 08:13 UTCGHSA enrichment
  23. 2026-08-16 19:14 UTCVendor advisory
  24. 2026-08-16 19:14 UTCGHSA enrichment
  25. 2026-08-16 06:14 UTCEG score recompute
Show 44 more
  1. 2026-08-16 06:14 UTCVendor advisory
  2. 2026-08-16 06:14 UTCGHSA enrichment
  3. 2026-08-16 02:14 UTCEPSS rescore
  4. 2026-08-15 17:16 UTCVendor advisory
  5. 2026-08-15 17:16 UTCGHSA enrichment
  6. 2026-08-15 04:17 UTCVendor advisory
  7. 2026-08-15 04:17 UTCGHSA enrichment
  8. 2026-08-14 15:17 UTCVendor advisory
  9. 2026-08-14 15:17 UTCGHSA enrichment
  10. 2026-08-14 02:18 UTCVendor advisory
  11. 2026-08-14 02:18 UTCGHSA enrichment
  12. 2026-08-13 13:19 UTCVendor advisory
  13. 2026-08-13 13:19 UTCGHSA enrichment
  14. 2026-08-13 00:19 UTCGHSA enrichment
  15. 2026-08-12 11:20 UTCVendor advisory
  16. 2026-08-12 11:20 UTCGHSA enrichment
  17. 2026-08-11 22:20 UTCEG score recompute
  18. 2026-08-11 22:20 UTCVendor advisory
  19. 2026-08-11 22:20 UTCGHSA enrichment
  20. 2026-08-11 13:42 UTCEPSS rescore
  21. 2026-08-11 09:20 UTCEG score recompute
  22. 2026-08-11 09:20 UTCGHSA enrichment
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-10 20:21 UTCGHSA enrichment
  25. 2026-08-10 07:22 UTCGHSA enrichment
  26. 2026-08-09 18:23 UTCGHSA enrichment
  27. 2026-08-09 05:24 UTCEG score recompute
  28. 2026-08-09 05:24 UTCGHSA enrichment
  29. 2026-08-08 16:37 UTCEPSS rescore
  30. 2026-08-08 16:25 UTCGHSA enrichment
  31. 2026-08-08 03:25 UTCEG score recompute
  32. 2026-08-08 03:25 UTCGHSA enrichment
  33. 2026-08-07 14:26 UTCGHSA enrichment
  34. 2026-08-07 13:51 UTCGHSA enrichment
  35. 2026-08-07 05:19 UTCGHSA enrichment
  36. 2026-08-07 04:18 UTCEG score recompute
  37. 2026-08-07 04:18 UTCGHSA enrichment
  38. 2026-08-07 02:17 UTCGHSA enrichment
  39. 2026-08-07 01:29 UTCEG score recompute▼ 1.40
  40. 2026-08-07 01:29 UTCGHSA enrichment
  41. 2026-08-07 01:28 UTCMITRE cvelistV5CVSS v3 → 7.4 · severity → HIGH
  42. 2026-08-06 22:19 UTCEG score recompute
  43. 2026-08-06 22:18 UTCNVD update
  44. 2026-08-06 22:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-19139?
CVE-2026-19139 is a high vulnerability published on August 6, 2026. Race in CredentialProvider in Google Chrome on Windows prior to 151.0.7922.109 allowed a local attacker to perform OS-level privilege escalation via a malicious file. (Chromium security severity: High)
When was CVE-2026-19139 disclosed?
CVE-2026-19139 was first published in the National Vulnerability Database on August 6, 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-19139 actively exploited?
CVE-2026-19139 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 99.4% of all scored CVEs.
What is the CVSS score of CVE-2026-19139?
CVE-2026-19139 has a CVSS v3.1 base score of 7.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-19139?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19139, 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-19139

Explore →

Is Your Infrastructure Affected by CVE-2026-19139?

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

Start Free Scan →Browse All CVEs