ChromeWeb browser · Google
CVE-2026-13281
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 · uneditedInteger overflow in Mojo in Google Chrome prior to 149.0.7827.201 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 confidenceAn integer overflow vulnerability in Mojo (Chromium's message passing library) in Google Chrome versions prior to 149.0.7827.201 allows a remote attacker who has already compromised the renderer process to potentially escape the Chrome sandbox via a malicious file, leading to arbitrary code execution on the host.
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.200CVSS 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.
-
Determine installed Google Chrome versionNavigate to chrome://version in the Chrome browser or type 'chrome --version' in command line. The version number is displayed next to 'Google Chrome' or the executable path.Affected if The displayed version is less than 149.0.7827.200 (for example, 149.0.7827.100 or any earlier version).
-
Verify Chrome is using the vulnerable Mojo componentMojo is included in standard Google Chrome installations. This check is implicit if Chrome is running. No additional configuration or flag is needed for the component to be present.Affected if Chrome is running and version is below 149.0.7827.200 - the Mojo component is present and vulnerable.
-
Confirm browser is not a hardened variantDetermine if the installed Chrome is a standard build (not Chromium-based forks like Brave, Edge, or managed enterprise builds with custom patching). Check the browser name in the title bar or via chrome://version.Affected if Standard Google Chrome version is below 149.0.7827.200. Note: Other Chromium-based browsers may have their own version numbering and may or may not be affected.
The user is affected if their Google Chrome version is below 149.0.7827.200, as the integer overflow in the Mojo message passing library can then be exploited to escape the sandbox.
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.200
Update Google Chrome to version 149.0.7827.201 or later. In enterprise environments, enforce automatic browser updates or deploy the patched version via centralized software distribution.
Chrome 149.0.7827.201 or later
- Open Google Chrome browser
- Click on the three-dot menu icon in the top-right corner
- Select 'Help' from the dropdown menu
- Click on 'About Google Chrome'
- The browser will automatically check for updates and display the current version
- If an update is available, click 'Update Google Chrome'
- Restart the browser to complete the update
- Verify the version by returning to Help > About Google Chrome and confirm it shows version 149.0.7827.201 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
- 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-13281 — 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-13281 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