ChromeWeb browser · Google
CVE-2026-11183
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 · uneditedOut of bounds read in GWP-ASan in Google Chrome prior to 149.0.7827.53 allowed a local attacker to obtain potentially sensitive information from process memory via a malicious file. (Chromium security severity: Medium)
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 confidenceOut of bounds read vulnerability in GWP-ASan (Google's memory safety detector) in Google Chrome prior to version 149.0.7827.53 allows a local attacker to read process memory and obtain potentially sensitive information by enticing a user to open a malicious file.
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.53CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 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 paths like /usr/bin/google-chrome or via package manager.Affected if Google Chrome is installed on the system
-
Determine installed Chrome versionOn Windows: Right-click Chrome shortcut > Properties > Details tab > Version, or enter chrome://settings/help in address bar. On macOS: Right-click app > Get Info > Version, or chrome://settings/help. On Linux: Run google-chrome --version or check package manager.Affected if Version shown is less than 149.0.7827.53
-
Verify version comparisonCompare the installed version number to the affected range: any version prior to 149.0.7827.53 is vulnerable. Note that version format may appear as 149.0.7827.53 or similar.Affected if Installed version is < 149.0.7827.53 (for example, 148.x.x.x or earlier)
-
Confirm GWP-ASan component is presentGWP-ASan is built into Chrome and cannot be disabled. It is automatically active in affected versions. No separate configuration check needed.Affected if Chrome version is vulnerable (version < 149.0.7827.53) - GWP-ASan is present and exploitable
A user is affected if Google Chrome is installed with any version prior to 149.0.7827.53, as the vulnerable GWP-ASan component is built into Chrome and active by default.
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.53
Update Google Chrome to version 149.0.7827.53 or later to remediate this vulnerability.
149.0.7827.53 or later
- Open Google Chrome
- Click the three-dot menu in the top-right corner
- Select 'Help' > 'About Google Chrome'
- Chrome will check for updates and automatically download version 149.0.7827.53 or later
- Click 'Relaunch' to apply the update
- Verify the version by returning to 'About Google Chrome' and confirming the version is 149.0.7827.53 or higher
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-11183 — 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-11183 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