CVE-2026-8583

Insufficient 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)

Published: 2026-05-14 Last update: 2026-05-19 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-8583 is rated Low Risk (27.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.06%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-8583

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-20 0.04% 0.06% +0.01%
2 2026-05-15 — 0.04% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-8583

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.6 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-8583

GitHub Security Advisory for CVE-2026-8583

GHSA-fh3c-f7qc-x6w8 · Severity: medium — Insufficient policy enforcement in WebXR in Google Chrome on Android prior to 148.0.7778.168...

OS Trackers for CVE-2026-8583

vendor priority summary link
debian end-of-life CVE-2026-8583 end-of-life priority: Debian including 1 source packages (chromium), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2026-8583
redhat medium — https://access.redhat.com/security/cve/CVE-2026-8583
ubuntu medium CVE-2026-8583 medium priority: Ubuntu including 1 source packages (chromium-browser), 5 status rows across 5 suites (jammy, noble, questing, resolute, upstream): not-affected 4, released 1. https://ubuntu.com/security/CVE-2026-8583

Affected software / configurations for CVE-2026-8583

Vendor Product Version Raw CPE
google chrome < 148.0.7778.168 cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*

References for CVE-2026-8583

cvelogic Threat Intelligence