VulnerabilityPublished 3 Feb 2026Updated 26 Feb 2026

CVE-2026-1861: Google Chrome · Heap Buffer Overflow

Affects Google ChromeSource CVE Database V5

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

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

8.8High

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

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

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 3 Feb 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 or the CVSS exploit maturity 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.132.

Affected software

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

AI-suggested

If you cannot patch yet, consider deploying browser security policies that restrict or sandbox video content processing, such as disabling or limiting VP8/VP9 codec usage where feasible. Employ network-level protections like web filtering and intrusion prevention systems to block access to suspicious or untrusted websites that could host malicious HTML content. Educate users about the risks of visiting untrusted websites and the importance of prompt browser updates. Utilize endpoint detection and response (EDR) tools to monitor for anomalous browser behavior indicative of exploitation attempts. For high-security environments, consider using browser isolation technologies to contain potential exploits. Maintain up-to-date threat intelligence feeds to detect emerging exploit attempts targeting this vulnerability. Finally, coordinate with IT and security teams to integrate vulnerability management workflows that ensure timely patch deployment and verification.

Description

Heap buffer overflow in libvpx in Google Chrome prior to 144.0.7559.132 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

Impact

The heap buffer overflow in libvpx within Chrome can lead to arbitrary code execution, enabling attackers to compromise the confidentiality, integrity, and availability of affected systems. Successful exploitation could allow attackers to execute malicious code remotely, potentially installing malware, stealing sensitive information, or disrupting user operations. Given Chrome's dominant market share as a web browser globally, the scope of affected systems is vast, impacting enterprises, governments, and individual users alike. The requirement for user interaction (visiting a malicious webpage) lowers the barrier for exploitation but still necessitates social engineering or drive-by download scenarios. The vulnerability's presence in a core multimedia processing library increases the risk of exploitation through common web content, making it a critical threat vector. Organizations relying heavily on Chrome for business operations face risks of data breaches, espionage, and service disruptions if unpatched. The absence of known exploits in the wild currently provides a window for proactive defense, but the high severity demands immediate attention to prevent future attacks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 07:50 UTC

Technical details

References

Community reviews

Related threats