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-5292: Out of bounds read in Google Chrome

0
Medium
VulnerabilityCVE-2026-5292cvecve-2026-5292
Published: Wed Apr 01 2026 (04/01/2026, 04:41:37 UTC)
Source: CVE Database V5
Vendor/Project: Google
Product: Chrome

Description

CVE-2026-5292 is an out-of-bounds read vulnerability in the WebCodecs component of Google Chrome versions prior to 146. 0. 7680. 178. This flaw allows a remote attacker to cause an out-of-bounds memory read by delivering a crafted HTML page, potentially exposing sensitive information from memory. The vulnerability does not require user authentication but does require user interaction to visit a malicious webpage. Although no known exploits are currently reported in the wild, the issue poses a medium risk due to its potential to leak information and the widespread use of Chrome globally. Google has addressed this vulnerability in version 146. 0. 7680.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/01/2026, 05:08:19 UTC

Technical Analysis

CVE-2026-5292 is a security vulnerability identified in the WebCodecs component of Google Chrome, specifically affecting versions prior to 146.0.7680.178. The flaw is an out-of-bounds read, which occurs when the browser processes specially crafted HTML content that triggers the WebCodecs API to read memory outside the intended bounds. This type of vulnerability can lead to the disclosure of sensitive information residing in adjacent memory areas, potentially including user data or other confidential information. The attack vector is remote and requires the victim to visit a maliciously crafted webpage, making it a client-side vulnerability. There is no indication that authentication is required, but user interaction (browsing to the malicious page) is necessary. Google has classified the severity as medium and has released a patch in version 146.0.7680.178 to remediate the issue. No public exploits have been reported yet, but the vulnerability's presence in a widely used browser component makes it a concern for a broad user base. The absence of a CVSS score necessitates an assessment based on impact and exploitability factors, which suggests a medium severity rating.

Potential Impact

The primary impact of CVE-2026-5292 is the potential unauthorized disclosure of information due to out-of-bounds memory reads. Attackers exploiting this vulnerability could gain access to sensitive data stored in memory, which might include personal user information, session tokens, or other confidential data processed by the browser. While this vulnerability does not directly allow code execution or system compromise, the leakage of sensitive information can facilitate further attacks such as phishing, session hijacking, or targeted exploitation. Given the ubiquity of Google Chrome as a web browser, the scope of affected systems is extensive, impacting individual users, enterprises, and public sector organizations worldwide. The requirement for user interaction (visiting a malicious webpage) limits automated exploitation but does not eliminate risk, especially in environments where users frequently browse untrusted or compromised websites. The medium severity reflects a balance between the potential data exposure and the exploitation complexity.

Mitigation Recommendations

To mitigate CVE-2026-5292, organizations and users should promptly update Google Chrome to version 146.0.7680.178 or later, where the vulnerability has been patched. Beyond patching, organizations should implement network-level protections such as web filtering and DNS filtering to block access to known malicious sites that could host exploit pages. Employing endpoint security solutions with behavioral detection can help identify suspicious browser activity indicative of exploitation attempts. Security teams should educate users about the risks of visiting untrusted websites and encourage cautious browsing habits. For high-risk environments, consider deploying browser isolation technologies that execute web content in a sandboxed environment, reducing the impact of client-side vulnerabilities. Continuous monitoring of threat intelligence feeds for any emerging exploits related to this CVE is also recommended to enable rapid response.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
Chrome
Date Reserved
2026-03-31T20:07:16.395Z
Cvss Version
null
State
PUBLISHED

Threat ID: 69cca4c4e6bfc5ba1d993171

Added to database: 4/1/2026, 4:53:24 AM

Last enriched: 4/1/2026, 5:08:19 AM

Last updated: 4/1/2026, 5:54:10 AM

Views: 2

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses