0.0
NA
CVE-2026-5279
Google Chrome V8 Object Corruption Vulnerability
Description

Object corruption in V8 in Google Chrome prior to 146.0.7680.178 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

INFO

Published Date :

April 1, 2026, 5:16 a.m.

Last Modified :

April 1, 2026, 5:16 a.m.

Remotely Exploit :

No
Affected Products

The following products are affected by CVE-2026-5279 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

No affected product recoded yet

Solution
Update Google Chrome to version 146.0.7680.178 or later to fix object corruption.
  • Update Google Chrome to the latest version.
  • Apply security patches for Chrome.
  • Ensure all users are updated.
Public PoC/Exploit Available at Github

CVE-2026-5279 has a 1 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-5279.

URL Resource
https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_31.html
https://issues.chromium.org/issues/490642836
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-5279 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-5279 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

None

Updated: 4 hours, 28 minutes ago
0 stars 0 fork 0 watcher
Born at : March 20, 2026, 7:22 a.m. This repo has been linked 1 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-5279 vulnerability anywhere in the article.

  • Daily CyberSecurity
Exploited in the Wild: Google Issues Emergency Patch for Chrome Zero-Day (CVE-2026-5281) in Dawn Component

Google has released a critical security update for the Chrome Stable channel to address 21 security vulnerabilities. While the patch covers a wide array of flaws, one particular bug has put security t ... Read more

Published Date: Apr 01, 2026 (2 hours, 45 minutes ago)

The following table lists the changes that have been made to the CVE-2026-5279 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • New CVE Received by [email protected]

    Apr. 01, 2026

    Action Type Old Value New Value
    Added Description Object corruption in V8 in Google Chrome prior to 146.0.7680.178 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
    Added Reference https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_31.html
    Added Reference https://issues.chromium.org/issues/490642836
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.