Out of bounds read in Media in Google Chrome prior to 149.0.7827.53 allowed an attacker on the local network segment to perform an out of bounds memory read via malicious network traffic. (Chromium security severity: Medium)
CVE-2026-10998
Score 4.0 from GitHub Security Advisory published 2026-06-05. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.0; 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
- 4.0
- Vendor severity
- MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
- EG Score
- 4.0(medium)
- EG Risk
- 18(Track)EG Risk 18/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 computedSeverity40% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 1%
- KEV
- Not listed
Published
June 4, 2026
Last Modified
July 22, 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.htmlVendor Advisories for CVE-2026-10998(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 ... 148.0.7778.96-3 (363 versions) | 149.0.7827.53-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 149.0.7827.53-1~deb12u1 (129 versions) | 149.0.7827.53-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.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 8× in last 7d / 32× 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 220 total refreshes for this CVE.
- 2026-09-16 05:14 UTCEPSS rescore
- 2026-09-14 05:15 UTCEG score recompute
- 2026-09-14 05:15 UTCVendor advisory
- 2026-09-14 05:15 UTCGHSA enrichment
- 2026-09-13 16:46 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 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-25 03:23 UTCEG score recompute
- 2026-08-25 03:23 UTCGHSA enrichment
- 2026-08-23 12:37 UTCVendor advisory
- 2026-08-23 12:37 UTCGHSA enrichment
- 2026-08-21 08:27 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-21 08:27 UTCVendor advisory
- 2026-08-21 08:27 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 09:52 UTCEG score recompute
- 2026-08-20 09:52 UTCVendor advisory
- 2026-08-20 09:52 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 10:47 UTCEG score recompute
- 2026-08-17 10:47 UTCVendor advisory
- 2026-08-17 10:47 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 12:26 UTCEG score recompute
- 2026-08-16 12:26 UTCVendor advisory
- 2026-08-16 12:26 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 14:05 UTCEG score recompute
- 2026-08-15 14:05 UTCVendor advisory
- 2026-08-15 14:05 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 06:19 UTCEG score recompute
- 2026-08-14 06:19 UTCVendor advisory
- 2026-08-14 06:19 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 07:58 UTCEG score recompute
- 2026-08-13 07:58 UTCVendor advisory
- 2026-08-13 07:57 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 08:57 UTCEG score recompute
- 2026-08-12 08:57 UTCVendor advisory
- 2026-08-12 08:57 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 10:36 UTCEG score recompute
- 2026-08-11 10:36 UTCVendor advisory
- 2026-08-11 10:36 UTCGHSA enrichment
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-10 12:14 UTCVendor advisory
- 2026-08-10 12:14 UTCGHSA enrichment
- 2026-08-09 13:52 UTCEG score recompute
- 2026-08-09 13:52 UTCVendor advisory
- 2026-08-09 13:52 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 15:31 UTCVendor advisory
- 2026-08-08 15:31 UTCGHSA enrichment
- 2026-08-07 17:09 UTCEG score recompute
- 2026-08-07 17:09 UTCVendor advisory
- 2026-08-07 17:09 UTCGHSA enrichment
- 2026-08-06 18:47 UTCEG score recompute
- 2026-08-06 18:47 UTCVendor advisory
- 2026-08-06 18:47 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 20:26 UTCEG score recompute
- 2026-08-05 20:26 UTCVendor advisory
- 2026-08-05 20:26 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 18:54 UTCEG score recompute
- 2026-08-04 18:54 UTCVendor advisory
- 2026-08-04 18:53 UTCGHSA enrichment
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-03 15:37 UTCEG score recompute
- 2026-08-03 15:37 UTCGHSA enrichment
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-02 10:41 UTCEG score recompute
- 2026-08-02 10:41 UTCVendor advisory
- 2026-08-02 10:41 UTCGHSA enrichment
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 12:17 UTCEG score recompute
- 2026-08-01 12:17 UTCVendor advisory
- 2026-08-01 12:17 UTCGHSA enrichment
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-31 05:22 UTCEG score recompute
- 2026-07-31 05:22 UTCVendor advisory
- 2026-07-31 05:22 UTCGHSA enrichment
- 2026-07-30 16:27 UTCEPSS rescore
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-10998?
When was CVE-2026-10998 disclosed?
Is CVE-2026-10998 actively exploited?
What is the CVSS score of CVE-2026-10998?
How do I remediate CVE-2026-10998?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-10998
Is Your Infrastructure Affected by CVE-2026-10998?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.