Out of bounds read in Codecs in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to obtain potentially sensitive information from process memory via a malicious file. (Chromium security severity: Medium)
CVE-2026-7981
This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- Vendor severity
- MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
- EG Score
- 8.1(medium)
- EG Risk
- 37(Track)EG Risk 37/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 computedSeverity81% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 10%
- KEV
- Not listed
Published
May 6, 2026
Last Modified
May 7, 2026
Advisory Details (2)
Auto-updated May 6, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop.htmlVendor Advisories for CVE-2026-7981(1)
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 ... 147.0.7727.55-1~deb13u1 (348 versions) | 148.0.7778.96-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 148.0.7778.96-1~deb12u1 (114 versions) | 148.0.7778.96-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 148.0.7778.96-1~deb13u1 (115 versions) | 148.0.7778.96-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 70× 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 200 total refreshes for this CVE.
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-30 19:18 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-24 14:18 UTCEPSS rescore
- 2026-08-23 19:44 UTCEG score recompute
- 2026-08-23 19:44 UTCVendor advisory
- 2026-08-23 19:44 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 12:50 UTCEG score recompute
- 2026-08-17 12:50 UTCVendor advisory
- 2026-08-17 12:50 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 04:49 UTCEG score recompute
- 2026-08-16 04:49 UTCVendor advisory
- 2026-08-16 04:49 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-14 16:19 UTCVendor advisory
- 2026-08-14 16:19 UTCGHSA enrichment
- 2026-08-14 03:22 UTCEG score recompute
- 2026-08-14 03:22 UTCVendor advisory
- 2026-08-14 03:22 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 06:02 UTCVendor advisory
- 2026-08-13 06:02 UTCGHSA enrichment
- 2026-08-12 16:57 UTCEG score recompute
- 2026-08-12 16:57 UTCVendor advisory
- 2026-08-12 16:57 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 15:58 UTCEG score recompute
- 2026-08-11 15:58 UTCVendor advisory
- 2026-08-11 15:58 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 01:28 UTCEG score recompute
- 2026-08-11 01:28 UTCVendor advisory
- 2026-08-11 01:28 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 04:24 UTCVendor advisory
- 2026-08-10 04:24 UTCGHSA enrichment
- 2026-08-09 15:28 UTCEG score recompute
- 2026-08-09 15:28 UTCGHSA enrichment
- 2026-08-09 13:47 UTCEPSS rescore
- 2026-08-09 02:31 UTCVendor advisory
- 2026-08-09 02:31 UTCGHSA enrichment
- 2026-08-08 03:45 UTCEG score recompute
- 2026-08-08 03:45 UTCVendor advisory
- 2026-08-08 03:45 UTCGHSA enrichment
- 2026-08-07 14:48 UTCVendor advisory
- 2026-08-07 14:48 UTCGHSA enrichment
- 2026-08-07 01:51 UTCEG score recompute
- 2026-08-07 01:51 UTCVendor advisory
- 2026-08-07 01:51 UTCGHSA enrichment
- 2026-08-06 13:47 UTCEPSS rescore
- 2026-08-06 11:14 UTCVendor advisory
- 2026-08-06 11:14 UTCGHSA enrichment
- 2026-08-05 22:17 UTCEG score recompute
- 2026-08-05 22:17 UTCVendor advisory
- 2026-08-05 22:17 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:39 UTCEPSS rescore
- 2026-08-03 19:46 UTCEG score recompute
- 2026-08-03 19:46 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 17:48 UTCVendor advisory
- 2026-08-02 17:48 UTCGHSA enrichment
- 2026-08-02 04:51 UTCEG score recompute
- 2026-08-02 04:51 UTCVendor advisory
- 2026-08-02 04:51 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:37 UTCEPSS rescore
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-24 14:18 UTCEPSS rescore
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:23 UTCEG score recompute▲ 1.60
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 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-7981?
When was CVE-2026-7981 disclosed?
Is CVE-2026-7981 actively exploited?
What is the CVSS score of CVE-2026-7981?
How do I remediate CVE-2026-7981?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-7981
Is Your Infrastructure Affected by CVE-2026-7981?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.