Out of bounds read in Chromoting in Google Chrome on Windows prior to 149.0.7827.155 allowed a local attacker to obtain potentially sensitive information from process memory via a malicious file. (Chromium security severity: High)
CVE-2026-12444
Score 5.5 from GitHub Security Advisory published 2026-06-17. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.5; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 5.5(medium)
- EG Risk
- 29(Track)EG Risk 29/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 computedSeverity55% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 4%
- KEV
- Not listed
Published
June 17, 2026
Last Modified
June 18, 2026
Advisory Details (2)
Auto-updated Jun 18, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_01750511403.htmlVendor Advisories for CVE-2026-12444(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 100.0.4896.127-1 ... 99.0.4844.84-1~deb11u1 (500 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 113.0.5672.126-1 ... 149.0.7827.53-1~deb13u1 (372 versions) | 149.0.7827.155-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 149.0.7827.53-1~deb13u1 (138 versions) | 149.0.7827.155-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 149.0.7827.53-1~deb13u1 (139 versions) | 149.0.7827.155-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 44× 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 236 total refreshes for this CVE.
- 2026-09-16 05:14 UTCEPSS rescore
- 2026-09-14 03:16 UTCEG score recompute
- 2026-09-14 03:16 UTCVendor advisory
- 2026-09-14 03:16 UTCGHSA enrichment
- 2026-09-13 16:46 UTCEPSS rescore
- 2026-09-12 15:00 UTCEPSS rescore
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 22:30 UTCEG score recompute
- 2026-08-30 22:30 UTCVendor advisory
- 2026-08-30 22:30 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:21 UTCEPSS rescore
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-27 14:24 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-24 22:30 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-24 22:30 UTCVendor advisory
- 2026-08-24 22:30 UTCGHSA enrichment
- 2026-08-23 08:58 UTCEG score recompute
- 2026-08-23 08:58 UTCVendor advisory
- 2026-08-23 08:58 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 06:22 UTCEG score recompute
- 2026-08-21 06:22 UTCVendor advisory
- 2026-08-21 06:22 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 08:24 UTCEG score recompute
- 2026-08-20 08:24 UTCVendor advisory
- 2026-08-20 08:24 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 08:18 UTCEG score recompute
- 2026-08-19 08:18 UTCVendor advisory
- 2026-08-19 08:18 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-16 21:17 UTCEG score recompute
- 2026-08-16 21:17 UTCVendor advisory
- 2026-08-16 21:17 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 22:00 UTCEG score recompute
- 2026-08-15 22:00 UTCVendor advisory
- 2026-08-15 22:00 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 23:59 UTCVendor advisory
- 2026-08-14 23:59 UTCGHSA enrichment
- 2026-08-14 02:09 UTCEG score recompute
- 2026-08-14 02:09 UTCVendor advisory
- 2026-08-14 02:09 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 04:20 UTCEG score recompute
- 2026-08-13 04:20 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 06:30 UTCEG score recompute
- 2026-08-12 06:30 UTCVendor advisory
- 2026-08-12 06:30 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 08:12 UTCEG score recompute
- 2026-08-11 08:12 UTCVendor advisory
- 2026-08-11 08:12 UTCGHSA enrichment
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-10 10:21 UTCEG score recompute
- 2026-08-10 10:20 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 12:31 UTCEG score recompute
- 2026-08-09 12:31 UTCVendor advisory
- 2026-08-09 12:31 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 14:41 UTCVendor advisory
- 2026-08-08 14:41 UTCGHSA enrichment
- 2026-08-07 16:51 UTCEG score recompute
- 2026-08-07 16:51 UTCVendor advisory
- 2026-08-07 16:51 UTCGHSA enrichment
- 2026-08-06 19:01 UTCEG score recompute
- 2026-08-06 19:01 UTCVendor advisory
- 2026-08-06 19:01 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 21:11 UTCEG score recompute
- 2026-08-05 21:11 UTCVendor advisory
- 2026-08-05 21:11 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 23:21 UTCEG score recompute
- 2026-08-04 23:21 UTCVendor advisory
- 2026-08-04 23:21 UTCGHSA enrichment
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-04 01:31 UTCEG score recompute
- 2026-08-04 01:31 UTCVendor advisory
- 2026-08-04 01:31 UTCGHSA enrichment
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-03 03:41 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-125
- CVE-2013-0767EG 10.0EPSS p93HIGH
- CVE-2009-2523EG 10.0EPSS p98HIGH
- CVE-2014-2898EG 9.8CRITICAL
- CVE-2014-2897EG 9.8CRITICAL
- CVE-2014-2896EG 9.8CRITICAL
- CVE-1999-0006EG 9.8EPSS p96CRITICAL
- CVE-2014-1522EG 9.3EPSS p92HIGH
- CVE-2013-0779EG 9.3EPSS p92HIGH
- CVE-2013-0778EG 9.3EPSS p90HIGH
- CVE-2012-3995EG 9.3EPSS p92HIGH
Frequently asked(5)
What is CVE-2026-12444?
When was CVE-2026-12444 disclosed?
Is CVE-2026-12444 actively exploited?
What is the CVSS score of CVE-2026-12444?
How do I remediate CVE-2026-12444?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-12444
Is Your Infrastructure Affected by CVE-2026-12444?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.