CVE-2026-13021: Inappropriate implementation in DeviceBoundSessionCredentials
Chromium: CVE-2026-13021 Inappropriate implementation in DeviceBoundSessionCredentials
Other sources
Inappropriate implementation in DeviceBoundSessionCredentials in Google Chrome prior to 149.0.7827.197 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: High)
— MITRE
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 149.0.7827.196 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 149.0.4022.96 - Upgrade
Upgrade
Google Chrome / Chromium-based (Edge inherits Chromium fixes)to a version that resolves this vulnerability.Fixed in 149.0.7827.197
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2026-13021?
CVE-2026-13021 has a medium severity rating of 4.3 according to the CVSS 3.1.
How do I fix CVE-2026-13021?
To fix CVE-2026-13021, users should update Google Chrome to version 149.0.7827.197 or later.
What does CVE-2026-13021 involve?
CVE-2026-13021 involves an inappropriate implementation in DeviceBoundSessionCredentials that could allow a remote attacker to bypass the same origin policy.
Which software is affected by CVE-2026-13021?
CVE-2026-13021 affects Google Chrome and Microsoft Edge (Chromium-based) versions prior to 149.0.7827.197.
When was CVE-2026-13021 published?
CVE-2026-13021 was published on May 10, 2026.