Out of bounds write in Skia in Google Chrome prior to 146.0.7680.75 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)
CVE-2026-3909
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-03-13), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- Vendor severity
- HIGHper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: High)
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
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 computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 2%
- EPSS %ILE
- 75%
- KEV
- ⚠ Exploited
Published
March 12, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Jul 27, 2026Known Exploited Vulnerabilities Catalog | CISA
Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-3909Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_13.htmlVendor Advisories for CVE-2026-3909(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 ... 146.0.7680.71-1~deb13u1 (324 versions) | 146.0.7680.80-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 146.0.7680.80-1~deb12u1 (90 versions) | 146.0.7680.80-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 146.0.7680.80-1~deb13u1 (91 versions) | 146.0.7680.80-1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 96× in last 7d / 388× 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 699 total refreshes for this CVE.
- 2026-09-20 00:26 UTCVendor advisory
- 2026-09-20 00:26 UTCGHSA enrichment
- 2026-09-19 20:03 UTCEG score recompute
- 2026-09-19 20:03 UTCVendor advisory
- 2026-09-19 20:03 UTCGHSA enrichment
- 2026-09-19 15:41 UTCVendor advisory
- 2026-09-19 15:41 UTCGHSA enrichment
- 2026-09-19 11:18 UTCVendor advisory
- 2026-09-19 11:18 UTCGHSA enrichment
- 2026-09-19 06:56 UTCVendor advisory
- 2026-09-19 06:56 UTCGHSA enrichment
- 2026-09-19 02:34 UTCVendor advisory
- 2026-09-19 02:34 UTCGHSA enrichment
- 2026-09-18 22:11 UTCEG score recompute
- 2026-09-18 22:11 UTCVendor advisory
- 2026-09-18 22:11 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 17:49 UTCVendor advisory
- 2026-09-18 17:49 UTCGHSA enrichment
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 13:27 UTCVendor advisory
- 2026-09-18 13:27 UTCGHSA enrichment
- 2026-09-18 09:05 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-18 09:05 UTCGHSA enrichment
- 2026-09-18 04:43 UTCVendor advisory
- 2026-09-18 04:43 UTCGHSA enrichment
- 2026-09-18 00:21 UTCVendor advisory
- 2026-09-18 00:21 UTCGHSA enrichment
- 2026-09-17 19:59 UTCEG score recompute
- 2026-09-17 19:59 UTCVendor advisory
- 2026-09-17 19:59 UTCGHSA enrichment
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-17 15:37 UTCVendor advisory
- 2026-09-17 15:37 UTCGHSA enrichment
- 2026-09-17 11:15 UTCVendor advisory
- 2026-09-17 11:15 UTCGHSA enrichment
- 2026-09-17 06:53 UTCVendor advisory
- 2026-09-17 06:53 UTCGHSA enrichment
- 2026-09-17 02:31 UTCVendor advisory
- 2026-09-17 02:31 UTCGHSA enrichment
- 2026-09-16 22:09 UTCVendor advisory
- 2026-09-16 22:09 UTCGHSA enrichment
- 2026-09-16 17:46 UTCEG score recompute
- 2026-09-16 17:46 UTCVendor advisory
- 2026-09-16 17:46 UTCGHSA enrichment
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 13:24 UTCVendor advisory
- 2026-09-16 13:23 UTCGHSA enrichment
- 2026-09-16 08:58 UTCEG score recompute
- 2026-09-16 08:58 UTCVendor advisory
- 2026-09-16 08:58 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-16 04:36 UTCVendor advisory
- 2026-09-16 04:36 UTCGHSA enrichment
- 2026-09-16 00:14 UTCVendor advisory
- 2026-09-16 00:14 UTCGHSA enrichment
- 2026-09-15 19:51 UTCVendor advisory
- 2026-09-15 19:51 UTCGHSA enrichment
- 2026-09-15 15:28 UTCVendor advisory
- 2026-09-15 15:28 UTCGHSA enrichment
- 2026-09-15 11:06 UTCVendor advisory
- 2026-09-15 11:06 UTCGHSA enrichment
- 2026-09-15 06:44 UTCEG score recompute
- 2026-09-15 06:44 UTCVendor advisory
- 2026-09-15 06:44 UTCGHSA enrichment
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-15 02:22 UTCVendor advisory
- 2026-09-15 02:22 UTCGHSA enrichment
- 2026-09-14 22:00 UTCVendor advisory
- 2026-09-14 21:59 UTCGHSA enrichment
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 17:37 UTCVendor advisory
- 2026-09-14 17:37 UTCGHSA enrichment
- 2026-09-14 13:15 UTCVendor advisory
- 2026-09-14 13:15 UTCGHSA enrichment
- 2026-09-14 08:53 UTCVendor advisory
- 2026-09-14 08:53 UTCGHSA enrichment
- 2026-09-14 04:31 UTCVendor advisory
- 2026-09-14 04:31 UTCGHSA enrichment
- 2026-09-14 00:09 UTCVendor advisory
- 2026-09-14 00:09 UTCGHSA enrichment
- 2026-09-13 19:45 UTCEG score recompute
- 2026-09-13 19:45 UTCVendor advisory
- 2026-09-13 19:45 UTCGHSA enrichment
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-13 15:23 UTCVendor advisory
- 2026-09-13 15:23 UTCGHSA enrichment
- 2026-09-13 11:01 UTCVendor advisory
- 2026-09-13 11:01 UTCGHSA enrichment
- 2026-09-13 06:39 UTCVendor advisory
- 2026-09-13 06:39 UTCGHSA enrichment
- 2026-09-13 02:17 UTCVendor advisory
- 2026-09-13 02:17 UTCGHSA enrichment
- 2026-09-12 21:56 UTCVendor advisory
- 2026-09-12 21:56 UTCGHSA enrichment
- 2026-09-12 17:34 UTCEG score recompute
- 2026-09-12 17:34 UTCVendor advisory
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Open source ↗GitHub PoCjaf0rk/CVE-2026-3909First seen Apr 10, 2026
Frequently asked(6)
What is CVE-2026-3909?
When was CVE-2026-3909 disclosed?
Is CVE-2026-3909 actively exploited?
What is the CVSS score of CVE-2026-3909?
Which products are affected by CVE-2026-3909?
How do I remediate CVE-2026-3909?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-3909
Is Your Infrastructure Affected by CVE-2026-3909?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.