Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-1861: Heap buffer overflow in Google Chrome

0
High
VulnerabilityCVE-2026-1861cvecve-2026-1861
Published: Tue Feb 03 2026 (02/03/2026, 20:56:47 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Chrome

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)

AI-Powered Analysis

AILast updated: 02/03/2026, 21:29:39 UTC

Technical Analysis

CVE-2026-1861 is a heap buffer overflow vulnerability identified in the libvpx library integrated within Google Chrome versions prior to 144.0.7559.132. Libvpx is a video codec library used for VP8/VP9 video decoding and encoding, which Chrome utilizes for media processing. The vulnerability arises when Chrome processes crafted HTML content that triggers a heap buffer overflow, leading to heap corruption. This memory corruption can be exploited by a remote attacker to execute arbitrary code within the context of the browser process. The attack vector involves a maliciously crafted HTML page that, when visited by a user, can trigger the overflow without requiring any user interaction beyond page load or rendering. Although no public exploits have been reported, the Chromium security team has rated this vulnerability as high severity due to the potential for remote code execution and the widespread use of Chrome. The vulnerability affects all platforms running the vulnerable Chrome versions, including Windows, macOS, and Linux. Because Chrome is a primary web browser in many organizations, this vulnerability poses a significant risk to confidentiality, integrity, and availability of systems and data accessed via the browser. The lack of a CVSS score means severity assessment must rely on the nature of the vulnerability, its exploitability, and potential impact. The vulnerability is mitigated by updating Chrome to version 144.0.7559.132 or later, which contains the necessary patches to fix the heap overflow in libvpx.

Potential Impact

For European organizations, the impact of CVE-2026-1861 can be substantial due to the widespread adoption of Google Chrome as a primary web browser. Successful exploitation could allow attackers to execute arbitrary code remotely, potentially leading to full compromise of the affected endpoint. This could result in data breaches, unauthorized access to sensitive information, disruption of business operations, and lateral movement within corporate networks. Sectors such as finance, government, healthcare, and critical infrastructure are particularly at risk given their reliance on secure web access and the high value of their data. The vulnerability's remote exploitation vector and lack of required authentication increase the risk of widespread attacks if weaponized. Additionally, the vulnerability could be leveraged in targeted attacks or drive-by download campaigns, increasing the threat surface for European enterprises. The absence of known exploits currently provides a window for proactive patching, but the high severity rating underscores the urgency. Organizations failing to update promptly may face increased exposure to advanced persistent threats and cybercriminal activity.

Mitigation Recommendations

European organizations should prioritize immediate patching of all Google Chrome installations to version 144.0.7559.132 or later to remediate the heap buffer overflow in libvpx. Beyond patching, organizations should implement network-level protections such as web filtering to block access to suspicious or untrusted websites that could host malicious HTML content. Employing endpoint detection and response (EDR) solutions with behavioral analysis can help detect exploitation attempts or anomalous browser behavior indicative of heap corruption. Security teams should conduct user awareness training emphasizing the risks of visiting untrusted sites and the importance of keeping browsers updated. Organizations may also consider deploying browser isolation technologies to contain potential exploitation within sandboxed environments. Regular vulnerability scanning and asset inventory management will ensure no vulnerable Chrome versions remain in use. Monitoring threat intelligence feeds for any emerging exploits related to CVE-2026-1861 will enable timely defensive adjustments. Finally, enforcing strict application whitelisting and least privilege principles can limit the impact of a successful exploit.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Chrome
Date Reserved
2026-02-03T20:25:08.273Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6982655ef9fa50a62fe085f1

Added to database: 2/3/2026, 9:15:10 PM

Last enriched: 2/3/2026, 9:29:39 PM

Last updated: 2/7/2026, 2:07:54 AM

Views: 259

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats