ChromeWeb browser · Google
CVE-2026-8583
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 · uneditedInsufficient policy enforcement in WebXR in Google Chrome on Android prior to 148.0.7778.168 allowed a remote attacker who had compromised the renderer process to obtain potentially sensitive information from process memory via a crafted HTML page. (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 confidenceInsufficient policy enforcement in WebXR on Chrome Android prior to version 148.0.7778.168 allows a remote attacker who has already compromised the renderer process to read potentially sensitive information from process memory via a crafted HTML page. This is an information disclosure vulnerability stemming from inadequate access controls in the WebXR Device API implementation.
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
< 148.0.7778.168CVSS 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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/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 Chrome for Android versionOpen Chrome app, tap the three dots menu, go to Settings > About Chrome to view the version numberAffected if Version is below 148.0.7778.168
-
Confirm WebXR API availabilityIn Chrome Android, navigate to chrome://flags and search for 'WebXR' to see if WebXR Device API features are enabled or exposed to web contentAffected if WebXR API is enabled and accessible to web pages
-
Verify device is AndroidConfirm the Chrome browser is running on an Android device (not iOS, desktop, or other platforms)Affected if Running Chrome on Android - this vulnerability only affects Android builds
You are affected if Chrome for Android is version 148.0.7778.168 or lower, WebXR is accessible on the device, and the attacker has already compromised the renderer process via other means.
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 · scoped148.0.7778.168
Update Google Chrome for Android to version 148.0.7778.168 or later. For enterprise environments, deploy the Chrome update through mobile device management (MDM) or enterprise mobility management (EMM) solutions to ensure fleet-wide coverage.
Chrome on Android version 148.0.7778.168 or later
- Open Google Play Store on the Android device
- Search for "Google Chrome" or locate it in your installed apps
- Tap on Chrome in the search results or app list
- If an update is available, tap the "Update" button
- Wait for the update to download and install
- Ensure the installed version is 148.0.7778.168 or later by checking: Open Chrome > Tap three dots > Tap Settings > Tap About Chrome
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8583 — 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-8583 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