ChromeWeb browser · Google
CVE-2026-13282
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 Payments in Google Chrome on Android prior to 149.0.7827.201 allowed a local attacker to potentially exploit heap corruption via physical access to the device. (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 confidenceA use-after-free vulnerability exists in the Payments component of Google Chrome on Android before version 149.0.7827.201. A local attacker with physical access to the device can potentially exploit heap corruption by manipulating memory after it has been freed, which may allow arbitrary code execution or further memory corruption.
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.201CVSS 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
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/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.
-
Confirm Google Chrome for Android is installedOpen the device Settings, go to Apps or Application Manager, and look for Google Chrome in the installed applications list.Affected if Google Chrome for Android appears in the installed apps
-
Locate the Chrome version numberOpen Google Chrome, tap the three-dot menu in the top right, go to Settings, then scroll down and tap About Chrome. The version number is displayed on that page.Affected if The version shown is a number less than 149.0.7827.201 (for example, 149.0.7827.200 or earlier)
-
Verify the Chrome build matches Android Chrome formatConfirm the version displayed includes the four-digit build number (such as 149.0.7827.200) rather than a different version scheme. Chrome for Android uses the format major.minor.build.patch.Affected if The version format matches the Android Chrome pattern but is below 149.0.7827.201
The device is affected if Google Chrome for Android is installed and its version number (found in About Chrome) is less than 149.0.7827.201.
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.201
Update Google Chrome for Android to version 149.0.7827.201 or later to patch the vulnerability. Restrict physical access to sensitive devices as a defense-in-depth measure.
Chrome 149.0.7827.201 or later on Android
- Open Google Play Store on the Android device
- Search for Google Chrome
- Tap Update to install the latest version, or verify Chrome is already updated to version 149.0.7827.201 or later
- Alternatively, check Chrome version by opening Chrome > tapping three dots > Settings > About Chrome to confirm the version
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
- 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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13282 — 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-13282 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