CVE-2026-5875

MEDIUMNVD 4.34.3—

4.3

Policy bypass in Blink in Google Chrome prior to 147.0.7727.55 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)

CVSS v3: 4.3
EG Score: 4.3(medium)
EPSS: 8.3%
KEV: Not listed

Published

April 8, 2026

Last Modified

April 13, 2026

References (2)

chrome-cve-admin@googlehttps://chromereleases.googleblog.com/2026/04/stable-channel-update-for-desktop.html
chrome-cve-admin@googlehttps://issues.chromium.org/issues/430198264

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-639Authorization Bypass Through User-Controlled Key (IDOR)

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Microsoft MSRCCVE-2026-58752026-04-11
Chromium: CVE-2026-5875 Policy bypass in Blink

Data Freshness Timeline

(refreshed 10× in last 7d / 16× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-26 13:44 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-21 22:43 UTCepss_batch
2026-05-20 22:38 UTCepss_batch
2026-05-20 18:14 UTCEG score recompute
2026-05-20 18:14 UTCVendor advisory
2026-05-20 18:14 UTCGHSA enrichment
2026-05-20 11:22 UTCepss_batch

Frequently asked(5)

What is CVE-2026-5875?

CVE-2026-5875 is a medium vulnerability published on April 8, 2026. Policy bypass in Blink in Google Chrome prior to 147.0.7727.55 allowed a remote attacker to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)

When was CVE-2026-5875 disclosed?

CVE-2026-5875 was first published in the National Vulnerability Database on April 8, 2026, with the most recent update on April 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2026-5875 actively exploited?

CVE-2026-5875 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2026-5875?

CVE-2026-5875 has a CVSS v3 base score of 4.3 (NVD).

How do I remediate CVE-2026-5875?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5875, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-5875

Explore →

Is Your Infrastructure Affected by CVE-2026-5875?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2026-5875

Published

Last Modified

References (2)

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2026-5875?

Same vendor

Same CWE

CVE-2026-5875

📅 Published

🔄 Last Modified

🔗 References (2)

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2026-5875?

🔗 Related CVEs(same vendor + same CWE)

Same vendor

Same CWE

Published

Last Modified

References (2)

Frequently asked(5)

Related CVEs(same vendor + same CWE)