CVE-2026-6313
published 2026-04-15CVE-2026-6313: Insufficient policy enforcement in CORS in Google Chrome prior to 147.0.7727.101 allowed a remote attacker who had compromised the renderer process to leak…
PriorityP411low3.1CVSS 3.1
AVNACHPRNUIRSUCLINAN
EPSS
0.21%
10.9th percentile
Insufficient policy enforcement in CORS in Google Chrome prior to 147.0.7727.101 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chrome | < 147.0.7727.101 | 147.0.7727.101 | |
| chrome | >= 147.0.7727.101 < 147.0.7727.101 | 147.0.7727.101 | |
| chrome_chrome | — | — |
CVSS provenance
nvdv3.13.1LOWCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
vendor_redhat3.1LOW
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Chrome
Stable Channel Update for ChromeOS / ChromeOS Flex: CVE-2026-6313
vendor_chrome·2026-04-22·CVSS 3.1
CVE-2026-6313 [LOW] Stable Channel Update for ChromeOS / ChromeOS Flex: CVE-2026-6313
Stable Channel Update for ChromeOS / ChromeOS Flex
CVE-2026-6313
Chrome
Stable Channel Update for Desktop: CVE-2026-6311
vendor_chrome·2026-04-15·CVSS 8.3
CVE-2026-6311 [HIGH] Stable Channel Update for Desktop: CVE-2026-6311
Stable Channel Update for Desktop
CVE-2026-6311: Uninitialized Use in Accessibility. Reported by Google on 2026-03-31 [N/A][ 498269651 ] High CVE-2026-6312: Insufficient policy enforcement in Passwords
Reported by Google on 2026-03-31 [N/A][ 498765210 ] High CVE-2026-6313: Insufficient policy enforcement in CORS
Severity: high
Red Hat
chromium-browser: Insufficient policy enforcement in CORS
vendor_redhat·2026-04-15·CVSS 3.1
CVE-2026-6313 [LOW] CWE-346 chromium-browser: Insufficient policy enforcement in CORS
chromium-browser: Insufficient policy enforcement in CORS
An insufficient policy enforcement flaw was found in the CORS component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=498765210
Statement: Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.
GHSA
GHSA-qcvg-hwr7-r9v7: Insufficient policy enforcement in CORS in Google Chrome prior to 147
ghsa_unreviewed·2026-04-15
CVE-2026-6313 [LOW] CWE-284 GHSA-qcvg-hwr7-r9v7: Insufficient policy enforcement in CORS in Google Chrome prior to 147
Insufficient policy enforcement in CORS in Google Chrome prior to 147.0.7727.101 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-6299 CVE-2026-6303 CVE-2026-6304 CVE-2026-6308 CVE-2026-6309 CVE-2026-6310 CVE-2026-6311 CVE-2026-6312 CVE-2026-6313 CVE-2026-6314 CVE-2026-6315 CVE-2026-6316 CVE-2026-6317 CVE-2026-6361 CVE-
bugzilla·2026-04-17·CVSS 8.8
CVE-2026-6299 [HIGH] CVE-2026-6299 CVE-2026-6303 CVE-2026-6304 CVE-2026-6308 CVE-2026-6309 CVE-2026-6310 CVE-2026-6311 CVE-2026-6312 CVE-2026-6313 CVE-2026-6314 CVE-2026-6315 CVE-2026-6316 CVE-2026-6317 CVE-2026-6361 CVE-
CVE-2026-6299 CVE-2026-6303 CVE-2026-6304 CVE-2026-6308 CVE-2026-6309 CVE-2026-6310 CVE-2026-6311 CVE-2026-6312 CVE-2026-6313 CVE-2026-6314 CVE-2026-6315 CVE-2026-6316 CVE-2026-6317 CVE-2026-6361 CVE-2026-6363 ... chromium: various flaws [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Bugzilla
CVE-2026-6299 CVE-2026-6303 CVE-2026-6304 CVE-2026-6308 CVE-2026-6309 CVE-2026-6310 CVE-2026-6311 CVE-2026-6312 CVE-2026-6313 CVE-2026-6314 CVE-2026-6315 CVE-2026-6316 CVE-2026-6317 CVE-2026-6361 CVE-
bugzilla·2026-04-17·CVSS 8.8
CVE-2026-6299 [HIGH] CVE-2026-6299 CVE-2026-6303 CVE-2026-6304 CVE-2026-6308 CVE-2026-6309 CVE-2026-6310 CVE-2026-6311 CVE-2026-6312 CVE-2026-6313 CVE-2026-6314 CVE-2026-6315 CVE-2026-6316 CVE-2026-6317 CVE-2026-6361 CVE-
CVE-2026-6299 CVE-2026-6303 CVE-2026-6304 CVE-2026-6308 CVE-2026-6309 CVE-2026-6310 CVE-2026-6311 CVE-2026-6312 CVE-2026-6313 CVE-2026-6314 CVE-2026-6315 CVE-2026-6316 CVE-2026-6317 CVE-2026-6361 CVE-2026-6363 ... chromium: various flaws [epel-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Bugzilla
CVE-2026-6313 Google Chrome: Chromium: Google Chrome: Cross-origin data leak via insufficient CORS policy enforcement
bugzilla·2026-04-15·CVSS 3.1
CVE-2026-6313 [LOW] CVE-2026-6313 Google Chrome: Chromium: Google Chrome: Cross-origin data leak via insufficient CORS policy enforcement
CVE-2026-6313 Google Chrome: Chromium: Google Chrome: Cross-origin data leak via insufficient CORS policy enforcement
Insufficient policy enforcement in CORS in Google Chrome prior to 147.0.7727.101 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
2026-04-15
Published