dbcve.org
ChromeWeb browser · Google

CVE-2026-14088

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 150.0.7871.47 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges 7 weeks old

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 · unedited
Uninitialized Use in Canvas in Google Chrome on Android prior to 150.0.7871.47 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Low)

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 confidence

Uninitialized Use vulnerability in Google Chrome's Canvas component on Android. A remote attacker can exploit this via a crafted HTML page to read potentially sensitive information from process memory due to the browser accessing uninitialized memory values.

MitigationUpdate Google Chrome for Android to version 150.0.7871.47 or later to patch the vulnerability.

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
Affected:< 150.0.7871.47

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Chrome for Android is installed
    Check your device's app list or settings under Apps > Chrome to confirm Google Chrome browser is installed on your Android device
    Affected if Chrome for Android is present on the device
  2. Locate the Chrome version number
    Open Chrome, tap the three-dot menu, go to Settings > About Chrome to display the current version number
    Affected if You can retrieve a version number from the About Chrome page
  3. Compare version against affected range
    Compare your installed version to the vulnerable range: any version below 150.0.7871.47 is affected
    Affected if The version shown is less than 150.0.7871.47 (for example, 150.0.7871.0 or earlier)
  4. Confirm Canvas feature usage
    The Canvas component is a standard HTML5 feature built into Chrome. Any web page using canvas elements (for example, games, graphics, video players) will trigger the vulnerable code path when processing uninitialized memory
    Affected if The browser processes HTML content with Canvas elements, which is common in many websites and web apps

You are affected if Google Chrome for Android is installed and its version is below 150.0.7871.47, as the uninitialized memory read in the Canvas component can be triggered when browsing web content.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 150.0.7871.47 or later
Fixed in 150.0.7871.47
Interim mitigation

Update Google Chrome for Android to version 150.0.7871.47 or later to patch the vulnerability.

Recommended fix High confidence

Chrome on Android version 150.0.7871.47 or later

  1. Open the Google Play Store app on the Android device
  2. Search for "Google Chrome" or locate it in the app list
  3. Tap on Google Chrome and select "Update" to install version 150.0.7871.47 or later
  4. Alternatively, enable automatic Chrome updates in the Google Play Store settings to ensure future security updates are applied promptly
  5. For enterprise-managed devices, use MDM/EMM tools to push the Chrome update to all enrolled Android devices
  6. Verify the update was successful by checking Chrome's version number in the app settings (Menu > Settings > About Chrome)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-14088 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-14088 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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