CVE-2026-8584: Inappropriate implementation in Views in Google Chrome on iOS prior to 148.0.7778.168 allowed a remote attacke

Routine

MEDIUM 4.2DOWNGRADE

CVE-2026-8584 is a medium-severity flaw (CVSS 4.2) affecting chrome. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Inappropriate implementation in Views in Google Chrome on iOS prior to 148.0.7778.168 allowed a remote attacker who had compromised the renderer process to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	4.2 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.1% (top 97%)
CISA exploited list	No
Weakness	CWE-451
Published	2026-05-14
Last modified	2026-10-25

Publisher (CNA): Chrome · Vendor: google

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-14 20:17 UTCPublished CVE record published
2026-10-25 23:10 UTCUpdated Record last modified

google chrome DOWNGRADE

Affected: 148.0.7778.168

Fixed in: no fixed release known

Safe to downgrade to: a release before 148.0.7778.168

1. Check installed version

apt-cache policy chrome || rpm -q chrome || chrome --version

2. No fixed release: DOWNGRADE to a release before 148.0.7778.168 (Debian / Ubuntu)

apt-cache madison chrome sudo apt install chrome=<VERSION_BEFORE_148.0.7778.168> sudo apt-mark hold chrome

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list chrome sudo dnf downgrade chrome-<VERSION_BEFORE_148.0.7778.168> sudo dnf versionlock add chrome

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-8584?

chrome: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2026-8584 being exploited?

CVE-2026-8584 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-8584 affect?

CVE-2026-8584 affects chrome. Severity is medium (CVSS 4.2). Inappropriate implementation in Views in Google Chrome on iOS prior to 148.0.7778.168 allowed a remote attacker who had compromised the renderer process to perform UI spoofing via a crafted HTML page. (Chromium security severity: Medium)

How urgent is CVE-2026-8584?

Priority 15/100. No elevated risk signals yet.

Software pages

iOS vulnerabilities · Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-6299 HIGH 8.8 UPGRADE Use after free in Prerender in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to execute arbi
CVE-2026-6300 HIGH 8.8 UPGRADE Use after free in CSS in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to execute arbitrary
CVE-2026-6307 HIGH 8.8 UPGRADE Type Confusion in Turbofan in Google Chrome prior to 147.0.7727.101 allowed a remote attacker to execute arbit
CVE-2026-8018 HIGH 8.1 UPGRADE Insufficient policy enforcement in DevTools in Google Chrome prior to 148.0.7778.96 allowed a remote attacker
CVE-2026-8016 HIGH 8.8 UPGRADE Use after free in WebRTC in Google Chrome prior to 148.0.7778.96 allowed a remote attacker to execute arbitrar

References

← Back to latest CVEs