CVE-2026-8585 json
Inappropriate implementation in Media in Google Chrome on iOS prior to 148.0.7778.168 allowed a remote attacker who had compromised the ren…
published 5mo ago modified 16d ago also EUVD-2026-30403
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
Inappropriate implementation in Media in Google Chrome on iOS prior to 148.0.7778.168 allowed a remote attacker who had compromised the renderer process to perform an out of bounds memory read via a crafted HTML page. (Chromium security severity: Medium)
Patch / fix
- google chrome 148.0.7778.168
- chromium Debian 12 148.0.7778.167-1~deb12u1
- chromium Debian 13 148.0.7778.167-1~deb13u1
- chromium Debian 14 148.0.7778.167-1
debian advisories DEBIAN-CVE-2026-8585
- chromium openSUSE Leap 16.0 148.0.7778.215-bp160.1.1
- chromium openSUSE Tumbleweed 148.0.7778.167-2.1
opensuse advisories openSUSE-SU-2026:20849-1openSUSE-SU-2026:10786-1
Is CVE-2026-8585 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 5mo ago
Exploit prediction
0.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-693 Protection Mechanism Failure
- Technology feeds
References
-
chromereleases.googleblog.com
/2026/05/stable-channel-update-for-desktop_12.html
vendor-advisory
-
issues.chromium.org
/issues/499052720
permissions-required
Sources
- CVE List CVE-2026-8585
- NVD CVE-2026-8585
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.