High

Heap Buffer Overflow in libvpx in Google Chrome

IdentifiersCVE-2026-1861CWE-122· Heap-based Buffer Overflow

CVE-2026-1861 is a high-severity heap buffer overflow in the libvpx video codec library used by Google Chrome and Chromium-based browsers. According to the provided content, affected versions are Google Chrome prior to 144.0.7559.132, and the issue can be triggered remotely via a crafted HTML page, likely by causing the browser to process malicious video content through libvpx. The flaw results in heap corruption in libvpx, with the browser update notes further indicating that a crafted video file could trigger the condition when processed. Specific vulnerable functions and root-cause implementation details are not available in the provided material because vendor details were intentionally restricted pending broad patch adoption.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can corrupt heap memory in the browser process and may lead to a crash, control-flow hijacking, browser compromise, or potentially arbitrary code execution in the context of the targeted Chrome process. The supplied advisories also note possible denial of service and, in broader Chromium packaging contexts, potential information disclosure depending on exploitation conditions.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure to untrusted web content by restricting browsing to trusted sites, applying web/network filtering, and using hardened or isolated browser execution environments such as sandboxing, VDI, or other application isolation controls. Because exploitation is described as remote via crafted web content, limiting access to attacker-controlled pages and media reduces risk but does not replace patching.

Remediation

Patch, then assume compromise.

Upgrade Google Chrome to version 144.0.7559.132 or later. For Chromium on Debian, apply the vendor security updates referenced in the provided content: 144.0.7559.109-2~deb12u1 for Debian 12 (bookworm) or 144.0.7559.109-2~deb13u1 for Debian 13 (trixie). More generally, deploy the latest vendor-provided Chromium/Chrome security update for the affected platform as soon as available.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

GoogleChromeapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

18 SOURCESView more in app

thecyberexpress com vulnerabilitiesNews

Feb 11, 2026

Microsoft Patch Tuesday February 2026 Fixes 6 Zero-Days

A Chrome/Chromium vulnerability (republished by Microsoft) that affects Chromium-based Microsoft Edge.

bleeping computerNews

Feb 10, 2026

Microsoft February 2026 Patch Tuesday fixes 6 zero-days, 58 flaws

A heap buffer overflow in Chromium's libvpx as referenced for Microsoft Edge (Chromium-based) (no additional details provided in the content).

zerodayinitiative blogNews

Feb 10, 2026

Zero Day Initiative - The February 2026 Security Update Review

A heap buffer overflow in Chromium's libvpx component that can lead to remote code execution.

the hacker newsNews

Feb 9, 2026

⚡ Weekly Recap: AI Skill Malware, 31Tbps DDoS, Notepad++ Hack, LLM Backdoors and More

Unknown (listed as a trending CVE affecting Google Chrome; no technical details provided in the content).

+4 more in the timeline

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity9

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES

MITRE CVE

cve.org · CVE-2026-1861

NVD

nvd.nist.gov/vuln/detail/CVE-2026-1861

MITRE CWE · CWE-122

Heap-based Buffer Overflow

Vendor Advisory

chromereleases.googleblog.com/2026/02/stable-channel-update-for-desktop.html

Permissions Required

issues.chromium.org/issues/478942410