ChromeWeb browser · Google
CVE-2026-12022
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 · uneditedRace in Safe Browsing in Google Chrome on Mac prior to 149.0.7827.115 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a malicious file. (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 confidenceA race condition in Safe Browsing in Google Chrome on Mac prior to version 149.0.7827.115 allowed a remote attacker who had already compromised the renderer process to potentially escape the sandbox via a malicious file. This is a high-severity Chromium security issue.
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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
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 Chrome version on MacOpen Chrome, click the Chrome menu → About Google Chrome, or run '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --version' in TerminalAffected if The displayed version is earlier than 149.0.7827.115 (e.g., 149.0.7827.100, 148.x.x.x, etc.)
-
Confirm Chrome is running on macOSThis vulnerability specifically affects Chrome on Mac. Verify the operating system by clicking the Apple menu → About This Mac, or run 'uname -a' in TerminalAffected if Chrome is running on any macOS version and the Chrome version is below 149.0.7827.115
-
Verify Safe Browsing is enabledOpen Chrome Settings → Privacy and security → Safe Browsing. Alternatively, inspect the Chrome preferences file at ~/Library/Application Support/Google/Chrome/Default/Preferences and look for 'safebrowsing' settings with 'enabled' set to trueAffected if Safe Browsing is enabled and the Chrome version is below 149.0.7827.115 - the race condition only applies when Safe Browsing is active
You are affected if you are running Google Chrome on Mac with a version earlier than 149.0.7827.115 and Safe Browsing is enabled, as the vulnerability requires the Safe Browsing feature to be active.
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 on Mac to version 149.0.7827.115 or later to patch the race condition vulnerability in Safe Browsing.
149.0.7827.115
- Open Google Chrome browser
- Click on the three-dot menu in the top-right corner
- Select 'Help' and then 'About Google Chrome'
- Chrome will automatically check for updates
- If version 149.0.7827.115 or later is available, click 'Update Google Chrome'
- Restart the browser to apply the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12022 — 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-12022 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