VulnerabilityPublished 20 Jan 2026Updated 26 Feb 2026

CVE-2026-0900: Google Chrome · Inappropriate Implementation

Affects Google ChromeSource CVE Database V5

Not known to be exploited · CVSS 8.8 High : upgrade to 144.0.7559.59 soon.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score

8.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 144.0.7559.59

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Google Chrome to 144.0.7559.59.

Affected software

Product	Affected	Fixed in
GoogleChrome	Affected >=144.0.7559.59 <144.0.7559.59	Fixed in 144.0.7559.59

AI-suggested

To mitigate CVE-2026-0900, organizations should immediately update all instances of Google Chrome to version 144.0.7559.59 or later, as this version contains the patch for the vulnerability. Beyond patching, organizations should enforce strict browser update policies and automate patch management to reduce exposure windows. Employing browser security features such as sandboxing, site isolation, and disabling unnecessary plugins can limit exploitation impact. Network-level protections like web filtering and intrusion prevention systems should be configured to block access to known malicious sites and suspicious content. User awareness training is critical to reduce the risk of social engineering attacks that lure users to malicious webpages. Monitoring browser behavior and network traffic for anomalies can help detect exploitation attempts early. For high-security environments, consider using browser isolation technologies or restricting the use of browsers to trusted sites only. Finally, maintain an incident response plan that includes steps for containment and remediation in case of compromise.

Description

Inappropriate implementation in V8 in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to potentially exploit object corruption via a crafted HTML page. (Chromium security severity: High)

Impact

The potential impact of CVE-2026-0900 is severe for organizations and individual users worldwide. Exploitation can lead to complete compromise of the affected system's confidentiality, integrity, and availability, enabling attackers to execute arbitrary code, steal sensitive data, or disrupt services. Since Google Chrome is one of the most widely used browsers globally, the attack surface is extensive, affecting enterprises, governments, and consumers alike. Attackers could leverage this vulnerability to deploy malware, conduct espionage, or launch further attacks within compromised networks. The requirement for user interaction (visiting a malicious webpage) means phishing or drive-by download attacks are likely vectors. Organizations relying heavily on web applications and browser-based workflows are particularly at risk. The lack of known exploits in the wild currently reduces immediate risk but does not diminish the urgency of patching, as exploit development is likely given the vulnerability's high severity and public disclosure.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 08:24 UTC

Technical details

References

Community reviews

Related threats