Skip to content
major vulnerability· requires attention

Widely-used Chrome browser; potential remote code execution via crafted HTML; impactful across many organizations

Web

CVE-2026-4454

8.8
High
EPSS 0.25%Patch availableMar 21, 2026

Use-after-free in Chrome networking allows remote heap corruption via crafted HTML.

common questions

Is CVE-2026-4454 being exploited?

Not confirmed. CVE-2026-4454 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.25% probability of exploitation in the next 30 days.

How severe is CVE-2026-4454?

CVE-2026-4454 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-4454?

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

What does CVE-2026-4454 affect?

CVE-2026-4454 affects Google Chrome <146.0.7680.153. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-4454?

Update Chrome to latest version; enable automatic updates.

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

executive summary
technical analysis
affected
Google Chrome <146.0.7680.153
impact

Remote code execution in the user's browser via crafted HTML page exploiting Chrome network use-after-free (heap corruption).

action required

Immediate action required

affected versions
Google Chrome
  • affected< 146.0.7680.153

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