Insufficient policy enforcement in DevTools in Google Chrome on Android prior to 150.0.7871.47 allowed a local attacker to bypass navigation restrictions via a malicious file. (Chromium security severity: Medium)
CVE-2026-13929
Score 5.5 from GitHub Security Advisory published 2026-07-01. 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
- MEDIUMper Google (Chromium)Vendor's own band, not a CVSS rating — advisory text: (Chromium security severity: Medium)
- 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 30, 2026
Last Modified
July 1, 2026
Advisory Details (2)
Auto-updated Jul 4, 2026Chrome Releases: Stable Channel Update for Desktop
https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.htmlVendor Advisories for CVE-2026-13929(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 (378 versions) | 150.0.7871.46-1~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 150.0.7871.46-1~deb12u1 (144 versions) | 150.0.7871.46-1~deb13u1 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| chromium | 138.0.7204.183-1 ... 150.0.7871.46-1~deb13u1 (145 versions) | 150.0.7871.46-1 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 100× 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 151 total refreshes for this CVE.
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-24 11:13 UTCEG score recompute
- 2026-08-24 11:13 UTCVendor advisory
- 2026-08-24 11:13 UTCGHSA enrichment
- 2026-08-23 07:44 UTCEG score recompute
- 2026-08-23 07:44 UTCVendor advisory
- 2026-08-23 07:44 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 07:56 UTCEG score recompute
- 2026-08-22 07:56 UTCVendor advisory
- 2026-08-22 07:56 UTCGHSA enrichment
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 04:52 UTCEG score recompute
- 2026-08-21 04:52 UTCVendor advisory
- 2026-08-21 04:52 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 05:06 UTCEG score recompute
- 2026-08-20 05:06 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 23:41 UTCEG score recompute
- 2026-08-18 23:41 UTCVendor advisory
- 2026-08-18 23:41 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 23:53 UTCEG score recompute
- 2026-08-17 23:53 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-17 23:53 UTCGHSA enrichment
- 2026-08-16 18:10 UTCEG score recompute
- 2026-08-16 18:10 UTCVendor advisory
- 2026-08-16 18:10 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 17:41 UTCEG score recompute
- 2026-08-15 17:41 UTCVendor advisory
- 2026-08-15 17:41 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 17:55 UTCEG score recompute
- 2026-08-14 17:55 UTCVendor advisory
- 2026-08-14 17:55 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 18:09 UTCVendor advisory
- 2026-08-13 18:09 UTCGHSA enrichment
- 2026-08-12 16:38 UTCEG score recompute
- 2026-08-12 16:38 UTCVendor advisory
- 2026-08-12 16:38 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-11 16:50 UTCEG score recompute
- 2026-08-11 16:50 UTCVendor advisory
- 2026-08-11 16:50 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-10 17:04 UTCGHSA enrichment
- 2026-08-09 17:09 UTCEG score recompute
- 2026-08-09 17:09 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-08 17:24 UTCEG score recompute
- 2026-08-08 17:24 UTCVendor advisory
- 2026-08-08 17:24 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 17:38 UTCEG score recompute
- 2026-08-07 17:38 UTCVendor advisory
- 2026-08-07 17:38 UTCGHSA enrichment
- 2026-08-06 17:52 UTCEG score recompute
- 2026-08-06 17:52 UTCVendor advisory
- 2026-08-06 17:52 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-05 18:05 UTCGHSA enrichment
- 2026-08-04 18:20 UTCEG score recompute
- 2026-08-04 18:20 UTCVendor advisory
- 2026-08-04 18:20 UTCGHSA enrichment
- 2026-08-04 15:09 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-03 18:22 UTCEG score recompute
- 2026-08-03 18:22 UTCGHSA enrichment
- 2026-08-03 10:35 UTCEPSS rescore
- 2026-08-02 18:34 UTCEG score recompute
- 2026-08-02 18:34 UTCVendor advisory
- 2026-08-02 18:34 UTCGHSA enrichment
- 2026-08-02 02:26 UTCEPSS rescore
- 2026-08-01 18:48 UTCEG score recompute
- 2026-08-01 18:48 UTCVendor advisory
- 2026-08-01 18:48 UTCGHSA enrichment
- 2026-08-01 04:15 UTCEPSS rescore
- 2026-07-31 19:02 UTCEG score recompute
- 2026-07-31 19:02 UTCVendor advisory
- 2026-07-31 19:02 UTCGHSA enrichment
- 2026-07-30 19:17 UTCEG score recompute
- 2026-07-30 19:16 UTCGHSA enrichment
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 18:12 UTCVendor advisory
- 2026-07-29 18:12 UTCGHSA enrichment
- 2026-07-28 18:22 UTCEG score recompute
- 2026-07-28 18:22 UTCVendor advisory
- 2026-07-28 18:22 UTCGHSA enrichment
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 16:12 UTCEG score recompute
- 2026-07-27 16:12 UTCVendor advisory
- 2026-07-27 16:12 UTCGHSA enrichment
- 2026-07-27 14:13 UTCEPSS rescore
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-20
- CVE-2005-0050EG 10.0EPSS p99HIGH
- CVE-2004-1019EG 10.0EPSS p94HIGH
- CVE-2004-0840EG 10.0EPSS p98HIGH
- CVE-2003-1425EG 10.0EPSS p96HIGH
- CVE-2003-1487EG 10.0EPSS p94HIGH
- CVE-2002-1874EG 10.0HIGH
- CVE-2002-2236EG 10.0EPSS p91HIGH
- CVE-2002-2365EG 10.0HIGH
- CVE-2002-1358EG 10.0EPSS p93HIGH
- CVE-2002-1359EG 10.0EPSS p100HIGH
Frequently asked(5)
What is CVE-2026-13929?
When was CVE-2026-13929 disclosed?
Is CVE-2026-13929 actively exploited?
What is the CVSS score of CVE-2026-13929?
How do I remediate CVE-2026-13929?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-13929
Is Your Infrastructure Affected by CVE-2026-13929?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.