ChromeWeb browser · Google
CVE-2026-13031
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 · uneditedUse after free in Blink in Google Chrome prior to 149.0.7827.197 allowed a remote attacker to execute arbitrary code inside a sandbox 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 confidenceUse-after-free vulnerability in Google Chrome's Blink rendering engine allows a remote attacker to execute arbitrary code inside the sandbox context by tricking users into visiting a crafted HTML page. The vulnerability exists in versions prior to 149.0.7827.197.
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.197CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 if Google Chrome is installedOn Windows, check for Chrome in Program Files or via Registry; on macOS, check /Applications/Google Chrome.app; on Linux, check common package locations or run 'google-chrome --version'Affected if Google Chrome is present on the endpoint
-
Retrieve the installed Chrome versionNavigate to chrome://settings/help in the Chrome browser, or run 'google-chrome --version' from command line on Linux/Mac, or check the version property of the Chrome executable on WindowsAffected if Unable to determine version (Chrome may not be fully installed)
-
Compare installed version against affected rangeParse the version number and compare numerically to 149.0.7827.197 - any version lower than this build is affectedAffected if Installed version is less than 149.0.7827.197
-
Verify Blink rendering engine is enabledThe Blink engine is built into Chrome and enabled by default - no user configuration required. This is automatically active for all Chrome users.Affected if Chrome is running at all (Blink is always enabled in Chrome)
The environment is affected if Google Chrome is installed with any version lower than 149.0.7827.197, as the use-after-free vulnerability in the Blink rendering engine will be present.
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.197
Update Google Chrome to version 149.0.7827.197 or later to patch the vulnerability. Organizations should deploy browser updates through their enterprise management systems and verify completion across affected endpoints.
Chrome version 149.0.7827.197 or later
- 1. Open Google Chrome browser
- 2. Navigate to Chrome menu (three dots) > Help > About Google Chrome
- 3. The browser will check for updates automatically
- 4. If version is older than 149.0.7827.197, download and install the update
- 5. Restart Chrome 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
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13031 — 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-13031 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