CVE-2026-8572: Insufficient policy enforcement in Network
Chromium: CVE-2026-8572 Insufficient policy enforcement in Network
Other sources
Insufficient policy enforcement in Network in Google Chrome on Android prior to 148.0.7778.168 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
— NVD
This CVE was assigned by Chrome. Microsoft Edge (Chromium-based) ingests Chromium, which addresses this vulnerability. Please see Google Chrome Releases for more information
— Microsoft
Credit
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 148.0.7778.167 - Upgrade
Upgrade
Chromium (Google Chrome on Android)to a version that resolves this vulnerability.Fixed in 148.0.7778.168 - Compensating control
If feasible, reduce exposure by preventing untrusted web content from executing in a compromised renderer process (e.g., avoid loading crafted/unknown HTML pages) until the Chromium/Chrome update to 148.0.7778.168 is applied.
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-8509
- CVE-2026-8510
- CVE-2026-8511
- CVE-2026-8512
- CVE-2026-8513
- CVE-2026-8514
- CVE-2026-8515
- CVE-2026-8516
- CVE-2026-8517
- CVE-2026-8518
- CVE-2026-8519
- CVE-2026-8520
- CVE-2026-8521
- CVE-2026-8522
- CVE-2026-8523
- CVE-2026-8558
- CVE-2026-8524
- CVE-2026-8525
- CVE-2026-8526
- CVE-2026-8527
- CVE-2026-8529
- CVE-2026-8530
- CVE-2026-8531
- CVE-2026-8532
- CVE-2026-8533
- CVE-2026-8534
- CVE-2026-8535
- CVE-2026-8536
- CVE-2026-8537
- CVE-2026-8538
- CVE-2026-8539
- CVE-2026-8540
- CVE-2026-8541
- CVE-2026-8542
- CVE-2026-8543
- CVE-2026-8544
- CVE-2026-8545
- CVE-2026-8546
- CVE-2026-8547
- CVE-2026-8548
- CVE-2026-8549
- CVE-2026-8550
- CVE-2026-8551
- CVE-2026-8552
- CVE-2026-8553
- CVE-2026-8554
- CVE-2026-8555
- CVE-2026-8556
- CVE-2026-8557
- CVE-2026-8559
- CVE-2026-8528
- CVE-2026-8560
- CVE-2026-8561
- CVE-2026-8562
- CVE-2026-8563
- CVE-2026-8564
- CVE-2026-8565
- CVE-2026-8566
- CVE-2026-8567
- CVE-2026-8569
- CVE-2026-8570
- CVE-2026-8571
- CVE-2026-8573
- CVE-2026-8574
- CVE-2026-8575
- CVE-2026-8576
- CVE-2026-8577
- CVE-2026-8578
- CVE-2026-8579
- CVE-2026-8580
- CVE-2026-8581
- CVE-2026-8582
- CVE-2026-8583
- CVE-2026-8584
- CVE-2026-8585
- CVE-2026-8586
- CVE-2026-8587
Frequently Asked Questions
What is the severity of CVE-2026-8572?
The severity of CVE-2026-8572 is rated low with a CVSS score of 3.1.
How do I fix CVE-2026-8572?
To fix CVE-2026-8572, update Google Chrome to version 148.0.7778.168 or later.
Who is affected by CVE-2026-8572?
CVE-2026-8572 affects Google Chrome on Android prior to version 148.0.7778.168.
What type of vulnerability is CVE-2026-8572?
CVE-2026-8572 is classified as an insufficient policy enforcement vulnerability.
What can an attacker do with CVE-2026-8572?
An attacker exploiting CVE-2026-8572 can leak cross-origin data via a crafted HTML page.