CVE-2026-6311
published 2026-04-15CVE-2026-6311: Uninitialized Use in Accessibility in Google Chrome on Windows prior to 147.0.7727.101 allowed a remote attacker who had compromised the renderer process to…
high8.3CVSS 3.1
AVNACHPRNUIRSCCHIHAH
Uninitialized Use in Accessibility in Google Chrome on Windows prior to 147.0.7727.101 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 | — | — |
VulDB
Google Chrome up to 147.0.7727.55 on Windows Accessibility uninitialized variable (ID 498201)
vuldb·2026-04-16·CVSS 8.3
CVE-2026-6311 [HIGH] Google Chrome up to 147.0.7727.55 on Windows Accessibility uninitialized variable (ID 498201)
A vulnerability has been found in Google Chrome on Windows and classified as problematic. Affected by this issue is some unknown functionality of the component Accessibility. This manipulation causes use of uninitialized variable.
This vulnerability is tracked as CVE-2026-6311. The attack is possible to be carried out remotely. No exploit exists.
The affected component should be upgraded.
GHSA
GHSA-vhh6-f54w-x5gw: Uninitialized Use in Accessibility in Google Chrome on Windows prior to 147
ghsa_unreviewed·2026-04-15
CVE-2026-6311 [HIGH] CWE-457 GHSA-vhh6-f54w-x5gw: Uninitialized Use in Accessibility in Google Chrome on Windows prior to 147
Uninitialized Use in Accessibility in Google Chrome on Windows prior to 147.0.7727.101 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
Red Hat
chromium-browser: Uninitialized Use in Accessibility
vendor_redhat·2026-04-15·CVSS 8.3
CVE-2026-6311 [HIGH] CWE-824 chromium-browser: Uninitialized Use in Accessibility
chromium-browser: Uninitialized Use in Accessibility
An uninitialized use flaw was found in the Accessibility component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=498201025
Statement: Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.
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
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-6311 Google Chrome: Chromium: Google Chrome: Sandbox escape via uninitialized use in Accessibility
bugzilla·2026-04-15·CVSS 8.3
CVE-2026-6311 [HIGH] CVE-2026-6311 Google Chrome: Chromium: Google Chrome: Sandbox escape via uninitialized use in Accessibility
CVE-2026-6311 Google Chrome: Chromium: Google Chrome: Sandbox escape via uninitialized use in Accessibility
Uninitialized Use in Accessibility in Google Chrome on Windows prior to 147.0.7727.101 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
2026-04-15
Published