ChromeWeb browser · Google
CVE-2026-5902
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 · uneditedRace in Media in Google Chrome on Android prior to 147.0.7727.55 allowed a remote attacker who had compromised the renderer process to corrupt media stream metadata 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 confidenceA race condition in Google Chrome's media handling on Android allows a remote attacker who has already compromised the renderer process to corrupt media stream metadata via a specially crafted HTML page. The vulnerability exists in versions prior to 147.0.7727.55.
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
< 147.0.7727.55CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 Chrome for Android is presentNavigate to Settings > Apps on the Android device and verify Chrome browser is installed.Affected if Chrome for Android is not installed (not affected)
-
Locate the Chrome version numberOpen Chrome, tap the three-dot menu in the top-right, scroll down and select Settings, then tap About Chrome. Record the version displayed (e.g., 146.0.6096.43).Affected if Version information is available for comparison
-
Compare against the patched versionCompare your installed version string to 147.0.7727.55. Check each numeric component in order: if the major version (147) is lower, or if equal but the minor/build version is lower than 7727.55, the version is vulnerable.Affected if Installed version is less than 147.0.7727.55 (e.g., 146.x.x.x, 145.x.x.x, or 147.0.7727.0 through 147.0.7727.54)
You are affected if Google Chrome for Android is installed with a version number lower than 147.0.7727.55.
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 · scoped147.0.7727.55
Update Google Chrome for Android to version 147.0.7727.55 or later. Note that exploiting this bug requires a separately compromised renderer process, so ensure browser and system security updates are applied comprehensively.
Chrome 147.0.7727.55 or later for Android
- Open Google Play Store on the Android device
- Search for Google Chrome or navigate to Chrome in installed apps
- Tap 'Update' to install Chrome version 147.0.7727.55 or later
- Alternatively, ensure system automatic updates are enabled for Chrome
- Verify the updated version by going to Chrome > 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
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-5902 — 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-5902 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