CVE-2026-10993 in Chromeinfo

Summary

by MITRE • 06/05/2026

Heap buffer overflow in Skia in Google Chrome prior to 149.0.7827.53 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page. (Chromium security severity: Medium)

Once again VulDB remains the best source for vulnerability data.

Analysis

by VulDB Data Team • 06/07/2026

This heap buffer overflow vulnerability resides within the Skia graphics library component that Google Chrome utilizes for rendering graphical elements on web pages. The flaw manifests when processing specially crafted HTML content that triggers improper memory handling during graphics rendering operations. The vulnerability falls under the category of memory corruption issues and can be classified as a CWE-121 heap-based buffer overflow according to the Common Weakness Enumeration catalog. Attackers can exploit this weakness by hosting a malicious webpage that, when rendered by the affected Chrome version, causes the browser to write beyond the bounds of allocated heap memory.

The technical execution of this attack requires remote code execution capabilities through a web-based vector, where a malicious actor crafts HTML content specifically designed to trigger the buffer overflow condition. When Chrome processes this crafted content, the Skia library fails to properly validate input boundaries, allowing an attacker to overwrite adjacent memory locations. This memory corruption can potentially expose sensitive information from process memory, including stack canaries, heap metadata, or other process-specific data that could aid in further exploitation attempts. The vulnerability represents a medium severity issue according to Chromium security guidelines, indicating potential for information disclosure without direct execution capabilities.

The operational impact of this vulnerability extends beyond simple information disclosure, as it can serve as a stepping stone for more sophisticated attacks. Attackers may leverage the leaked memory information to bypass security mitigations such as address space layout randomization or stack canaries, making subsequent exploitation attempts more successful. The affected Chrome versions prior to 149.0.7827.53 represent a significant attack surface given Chrome's widespread usage across enterprise and consumer environments. This vulnerability aligns with ATT&CK technique T1059.001 for remote code execution through web-based attacks and T1566 for initial access via malicious websites.

Mitigation strategies should prioritize immediate patching of affected Chrome installations to version 149.0.7827.53 or later, which contains the necessary fixes for the heap buffer overflow condition. Organizations should implement network-based protections such as web application firewalls that can detect and block known malicious HTML patterns, while also maintaining up-to-date browser security policies that enforce secure rendering practices. Browser hardening measures including sandboxing, strict memory access controls, and heap memory protection mechanisms should be enabled to limit the potential impact of any successful exploitation attempts. Security monitoring should focus on detecting unusual memory access patterns or unexpected behavior in browser processes that might indicate exploitation attempts. Additionally, regular security assessments and penetration testing should verify that the patched environment properly handles the vulnerable code paths, ensuring that the remediation effectively addresses the root cause of the heap buffer overflow in the Skia graphics library component.

Responsible

Chrome

Reservation

06/04/2026

Disclosure

06/05/2026

Moderation

accepted

CPE

ready

EPSS

0.00033

KEV

no

Activities

very low

Sources

Want to know what is going to be exploited?

We predict KEV entries!