ChromeWeb browser · Google
CVE-2026-12448
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 · uneditedInappropriate implementation in WebView in Google Chrome on Android prior to 149.0.7827.155 allowed a remote attacker to perform privilege escalation 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 · moderate confidenceA vulnerability in Google Chrome's WebView component on Android allows a remote attacker to perform privilege escalation via a crafted HTML page. The 'inappropriate implementation' suggests a security boundary bypass within the WebView sandbox that could allow a malicious webpage to gain elevated access.
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.155CVSS 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 installed on the Android deviceOpen device Settings > Apps > Chrome, or look for Chrome in the app drawer. If Chrome is not installed, this specific CVE may not apply directly.Affected if Google Chrome app is installed on the Android device and its version is less than 149.0.7827.155
-
Determine the installed Chrome version on AndroidOpen Chrome app, tap the three-dot menu > Settings > About Chrome. The version number is displayed on this page.Affected if The displayed version number is below 149.0.7827.155 (for example, 149.0.7827.150 or any earlier version)
-
Confirm WebView is using Chrome as the provider (optional context)On Android 7.0 and later, check Settings > Apps > Chrome. If Chrome is listed as a WebView provider, it may be handling WebView rendering for other apps.Affected if Chrome serves as the WebView provider and its version is vulnerable, potentially expanding the attack surface to other apps using WebView
A user is affected if Google Chrome for Android is installed and its version is lower than 149.0.7827.155, as the WebView component in those versions contains the privilege escalation vulnerability.
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.155
Update Google Chrome for Android to version 149.0.7827.155 or later. Organizations should ensure managed devices receive the Chrome update through their MDM/EMM solution.
Chrome for Android version 149.0.7827.155 or later
- 1. Open the Google Play Store app on the Android device
- 2. Search for "Google Chrome" or "Chrome"
- 3. Tap on Chrome from the search results
- 4. If an update is available, tap the "Update" button
- 5. Wait for the update to download and install
- 6. Alternatively, ensure Android system WebView is updated by going to Settings > Apps > Android System WebView and checking for updates
- 7. After updating, restart Chrome or the device to ensure the fix takes effect
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-12448 — 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-12448 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