CVE-2026-11103

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
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: None knownExposed: 0

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

Inappropriate implementation in Installer in Google Chrome on Windows prior to 149.0.7827.53 allowed a local attacker to perform OS-level privilege escalation via a malicious file. (Chromium security severity: Medium)

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

Published

June 4, 2026

Last Modified

July 23, 2026

Advisory Details (2)

Auto-updated Jun 6, 2026
No patch confirmed yet.
generic

Chromium

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

Chrome Releases: Stable Channel Update for Desktop

https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html

Vendor Advisories for CVE-2026-11103(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 (500 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
chromium113.0.5672.126-1 ... 148.0.7778.96-3 (363 versions)149.0.7827.53-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 149.0.7827.53-1~deb12u1 (129 versions)149.0.7827.53-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
chromium138.0.7204.183-1 ... 149.0.7827.53-1~deb13u1 (130 versions)149.0.7827.53-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 88× 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.

Showing the most recent 100 of 251 total refreshes for this CVE.

  1. 2026-08-28 21:40 UTCEPSS rescore
  2. 2026-08-25 13:48 UTCEPSS rescore
  3. 2026-08-25 02:19 UTCEG score recompute
  4. 2026-08-25 02:19 UTCGHSA enrichment
  5. 2026-08-23 12:35 UTCEG score recompute
  6. 2026-08-23 12:35 UTCVendor advisory
  7. 2026-08-23 12:35 UTCGHSA enrichment
  8. 2026-08-23 00:19 UTCEPSS rescore
  9. 2026-08-22 01:59 UTCVendor advisory
  10. 2026-08-22 01:59 UTCGHSA enrichment
  11. 2026-08-21 13:12 UTCEG score recompute
  12. 2026-08-21 13:12 UTCVendor advisory
  13. 2026-08-21 13:12 UTCGHSA enrichment
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-20 22:35 UTCVendor advisory
  16. 2026-08-20 22:35 UTCGHSA enrichment
  17. 2026-08-20 09:49 UTCVendor advisory
  18. 2026-08-20 09:49 UTCGHSA enrichment
  19. 2026-08-17 03:44 UTCVendor advisory
  20. 2026-08-17 03:44 UTCGHSA enrichment
  21. 2026-08-16 14:58 UTCEG score recompute
  22. 2026-08-16 14:58 UTCVendor advisory
  23. 2026-08-16 14:58 UTCGHSA enrichment
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-16 02:12 UTCVendor advisory
Show 75 more
  1. 2026-08-16 02:12 UTCGHSA enrichment
  2. 2026-08-15 13:26 UTCVendor advisory
  3. 2026-08-15 13:26 UTCGHSA enrichment
  4. 2026-08-15 00:21 UTCVendor advisory
  5. 2026-08-15 00:21 UTCGHSA enrichment
  6. 2026-08-14 11:34 UTCVendor advisory
  7. 2026-08-14 11:34 UTCGHSA enrichment
  8. 2026-08-13 22:48 UTCVendor advisory
  9. 2026-08-13 22:48 UTCGHSA enrichment
  10. 2026-08-13 10:01 UTCVendor advisory
  11. 2026-08-13 10:01 UTCGHSA enrichment
  12. 2026-08-12 21:14 UTCGHSA enrichment
  13. 2026-08-12 08:19 UTCVendor advisory
  14. 2026-08-12 08:19 UTCGHSA enrichment
  15. 2026-08-11 16:52 UTCEG score recompute
  16. 2026-08-11 16:52 UTCVendor advisory
  17. 2026-08-11 16:52 UTCGHSA enrichment
  18. 2026-08-11 13:42 UTCEPSS rescore
  19. 2026-08-11 04:06 UTCVendor advisory
  20. 2026-08-11 04:06 UTCGHSA enrichment
  21. 2026-08-10 15:20 UTCGHSA enrichment
  22. 2026-08-10 02:34 UTCVendor advisory
  23. 2026-08-10 02:34 UTCGHSA enrichment
  24. 2026-08-09 13:48 UTCVendor advisory
  25. 2026-08-09 13:48 UTCGHSA enrichment
  26. 2026-08-09 01:02 UTCEG score recompute
  27. 2026-08-09 01:02 UTCVendor advisory
  28. 2026-08-09 01:02 UTCGHSA enrichment
  29. 2026-08-08 16:37 UTCEPSS rescore
  30. 2026-08-08 12:16 UTCVendor advisory
  31. 2026-08-08 12:16 UTCGHSA enrichment
  32. 2026-08-07 23:30 UTCEG score recompute
  33. 2026-08-07 23:30 UTCVendor advisory
  34. 2026-08-07 23:30 UTCGHSA enrichment
  35. 2026-08-07 10:44 UTCVendor advisory
  36. 2026-08-07 10:44 UTCGHSA enrichment
  37. 2026-08-06 21:57 UTCEG score recompute
  38. 2026-08-06 21:57 UTCVendor advisory
  39. 2026-08-06 21:57 UTCGHSA enrichment
  40. 2026-08-06 13:46 UTCEPSS rescore
  41. 2026-08-06 09:11 UTCVendor advisory
  42. 2026-08-06 09:11 UTCGHSA enrichment
  43. 2026-08-05 20:24 UTCEG score recompute
  44. 2026-08-05 20:24 UTCVendor advisory
  45. 2026-08-05 20:24 UTCGHSA enrichment
  46. 2026-08-05 19:17 UTCEPSS rescore
  47. 2026-08-04 18:48 UTCEG score recompute
  48. 2026-08-04 18:48 UTCVendor advisory
  49. 2026-08-04 18:48 UTCGHSA enrichment
  50. 2026-08-04 15:09 UTCEPSS rescore
  51. 2026-08-04 04:18 UTCGHSA enrichment
  52. 2026-08-03 15:32 UTCVendor advisory
  53. 2026-08-03 15:31 UTCGHSA enrichment
  54. 2026-08-03 02:18 UTCVendor advisory
  55. 2026-08-03 02:18 UTCGHSA enrichment
  56. 2026-08-02 13:32 UTCVendor advisory
  57. 2026-08-02 13:32 UTCGHSA enrichment
  58. 2026-08-02 00:46 UTCVendor advisory
  59. 2026-08-02 00:46 UTCGHSA enrichment
  60. 2026-08-01 12:00 UTCEG score recompute
  61. 2026-08-01 12:00 UTCVendor advisory
  62. 2026-08-01 11:59 UTCGHSA enrichment
  63. 2026-08-01 04:15 UTCEPSS rescore
  64. 2026-07-31 18:16 UTCVendor advisory
  65. 2026-07-31 18:16 UTCGHSA enrichment
  66. 2026-07-31 05:20 UTCEG score recompute
  67. 2026-07-31 05:20 UTCVendor advisory
  68. 2026-07-31 05:20 UTCGHSA enrichment
  69. 2026-07-30 16:27 UTCEPSS rescore
  70. 2026-07-29 09:51 UTCEG score recompute
  71. 2026-07-29 09:51 UTCVendor advisory
  72. 2026-07-29 09:51 UTCGHSA enrichment
  73. 2026-07-28 15:36 UTCEPSS rescore
  74. 2026-07-28 03:14 UTCEG score recompute
  75. 2026-07-28 03:14 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-11103?
CVE-2026-11103 is a high vulnerability published on June 4, 2026. Inappropriate implementation in Installer in Google Chrome on Windows prior to 149.0.7827.53 allowed a local attacker to perform OS-level privilege escalation via a malicious file. (Chromium security severity: Medium)
When was CVE-2026-11103 disclosed?
CVE-2026-11103 was first published in the National Vulnerability Database on June 4, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11103 actively exploited?
CVE-2026-11103 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-11103?
CVE-2026-11103 has a CVSS v3.1 base score of 7.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-11103?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11103, 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-11103

Explore →

Is Your Infrastructure Affected by CVE-2026-11103?

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

Start Free Scan →Browse All CVEs