ChromeWeb browser · Google
CVE-2026-12024
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsufficient policy enforcement in DevTools in Google Chrome prior to 149.0.7827.115 allowed a remote attacker to bypass same origin policy via a crafted HTML page. (Chromium security severity: High)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceInsufficient policy enforcement in Chrome's DevTools allowed a remote attacker to bypass Same Origin Policy (SOP) via a crafted HTML page. The vulnerability existed in DevTools prior to version 149.0.7827.115, enabling potentially malicious pages to access resources across different origins that should be protected by SOP.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 149.0.7827.115CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Google Chrome versionNavigate to chrome://settings/help or use the menu Help > About Google Chrome to view the current version numberAffected if Version number is lower than 149.0.7827.115
-
Verify Chrome channelOpen chrome://settings/help and note if the browser is on Stable, Beta, Dev, or Canary channelAffected if Browser is on Stable channel but version is below 149.0.7827.115, or on Beta/Dev/Canary with older version numbers
-
Confirm DevTools accessibilityOpen DevTools via F12, Ctrl+Shift+I, or right-click > Inspect while browsing any webpageAffected if DevTools can be opened and the browser version is vulnerable
-
Check for enterprise policy enforcementNavigate to chrome://policy to see if any group policies restrict DevTools usageAffected if No policy restrictions are in place and browser version is vulnerable
A user is affected if their Google Chrome version is below 149.0.7827.115 and they can access DevTools while browsing web content.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped149.0.7827.115
Update Google Chrome to version 149.0.7827.115 or later. For enterprise environments, deploy the update via centralized patch management and verify the browser version across affected systems.
Chrome 149.0.7827.115 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome to check the current version
- If the version is earlier than 149.0.7827.115, click 'Update Google Chrome' to download and install the latest version
- Restart the browser after the update completes to apply the fix
- Verify the version now shows 149.0.7827.115 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12024 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12024 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data