Secuno
ENNL
Book demo

CVE-2026-78934

8.3 HIGHEPSS 0.38%
  1. Published25 Aug 2026

Description

Race condition in ReadAloud in Google Chrome prior to 152.0.7977.65 allowed a remote attacker leveraging social engineering to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityHigh
Privileges requiredNone
User interactionRequired
ScopeChanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Affected products

Google Chrome< 152.0.7977.65

Remediation

Fixed in
Google Chrome≥ 152.0.7977.65

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-553188.8
In multiple locations, there is a possible use-after-free due to a race condition. This…
CVE-2026-654158.1
A race condition was addressed with additional validation. This issue is fixed in iOS…
CVE-2026-874678.1
Race condition in Updater in Google Chrome on on Windows prior to 153.0.8010.36 allowed…
CVE-2026-698278.1
Concurrent execution using shared resource with improper synchronization ('race…
CVE-2026-697828.1
Concurrent execution using shared resource with improper synchronization ('race…
CVE-2026-593248.2
When an IntegrationFlow uses .fluxTransform() with an asynchronous/reordering…

Frequently asked

Is CVE-2026-78934 being actively exploited?

CVE-2026-78934 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.38%.

How severe is CVE-2026-78934?

CVE-2026-78934 has a CVSS 3.1 base score of 8.3, rated high. EPSS estimates a 0.38% probability of exploitation.

Which products are affected by CVE-2026-78934?

Affected products include Google Chrome.

How do I fix CVE-2026-78934?

Upgrade affected software to a fixed version, for example Google Chrome 152.0.7977.65 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-78934 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.