CVE-2026-102300: Uninitialized resource in WebGPU in Google Chrome prior to 154.0.8037.92 allowed a remote attacker to obtain c

Routine

MEDIUM 4.3DOWNGRADE

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

Uninitialized resource in WebGPU in Google Chrome prior to 154.0.8037.92 allowed a remote attacker to obtain cross-origin data via a crafted HTML page. (Chromium security severity: High)

Why this priority

No elevated risk signals yet

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

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-908
Published	2026-09-29
Last modified	2026-10-01

Publisher (CNA): Chrome · Vendor: google

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

Am I affected?

Timeline

2026-09-29 20:17 UTCPublished CVE record published
2026-10-01 17:28 UTCUpdated Record last modified

google chrome DOWNGRADE

Affected: 154.0.8037.92

Fixed in: no fixed release known

Safe to downgrade to: a release before 154.0.8037.92

1. Check installed version

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

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

apt-cache madison chrome sudo apt install chrome=<VERSION_BEFORE_154.0.8037.92> sudo apt-mark hold chrome

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

dnf --showduplicates list chrome sudo dnf downgrade chrome-<VERSION_BEFORE_154.0.8037.92> 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.

Advisories and coverage

Official advisories

Chrome Enterprise Release Notes: Stable Channel Update for ChromeOS / ChromeOS Flex 2026-10-09
Chrome Enterprise Release Notes: Stable Channel Update for Desktop 2026-09-29

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-102300?

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

Is CVE-2026-102300 being exploited?

CVE-2026-102300 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-102300 affect?

CVE-2026-102300 affects chrome. Severity is medium (CVSS 4.3). Uninitialized resource in WebGPU in Google Chrome prior to 154.0.8037.92 allowed a remote attacker to obtain cross-origin data via a crafted HTML page. (Chromium security severity: High)

How urgent is CVE-2026-102300?

Priority 20/100. No elevated risk signals yet.

Software pages

Google Chrome vulnerabilities · Chromium vulnerabilities

Related CVEs

CVE-2026-113344 HIGH 8.8 UPGRADE Use after free in Performance in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to execute arb
CVE-2026-8510 HIGH 7.5 UPGRADE Integer overflow in Skia in Google Chrome on Windows prior to 148.0.7778.168 allowed a remote attacker who had
CVE-2026-8517 HIGH 8.8 UPGRADE Object lifecycle issue in WebShare in Google Chrome on Mac prior to 148.0.7778.168 allowed a remote attacker w
CVE-2026-8509 HIGH 8.8 UPGRADE Heap buffer overflow in WebML in Google Chrome prior to 148.0.7778.168 allowed a remote attacker to execute ar
CVE-2026-8524 HIGH 8.8 UPGRADE Out of bounds write in WebAudio in Google Chrome prior to 148.0.7778.168 allowed a remote attacker to execute

References

← Back to latest CVEs