Skip to content
major vulnerability· requires attention

Remote RCE in Google Chrome's V8 affects a widely used browser across enterprises; broad impact and newsworthy risk.

Applications

CVE-2026-17725

8.8
High
EPSS 0.52%Patch availableJul 31, 2026

Type confusion in V8 enables remote code execution in Chrome <151.0.7922.72

common questions

Is CVE-2026-17725 being exploited?

Not confirmed. CVE-2026-17725 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.52% probability of exploitation in the next 30 days.

How severe is CVE-2026-17725?

CVE-2026-17725 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-17725?

Yes. A fix has been recorded for CVE-2026-17725. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-17725 affect?

CVE-2026-17725 affects Google Chrome <151.0.7922.72, Chromium V8 JavaScript engine, Chromium-based browsers (potentially). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-17725?

Update Chrome to 151.0.7922.72 or later and enforce enterprise patching.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Google Chrome <151.0.7922.72Chromium V8 JavaScript engineChromium-based browsers (potentially)
impact

Remote code execution in Chrome renderer via crafted HTML, allowing arbitrary code to run in a sandboxed process.

action required

Immediate action required

affected versions
Google Chrome
  • affected< 151.0.7922.72

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free