What is the CVSS score of CVE-2026-7923?

CVE-2026-7923 has a CVSS 3.1 base score of 8.3 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Google Chrome are affected by CVE-2026-7923?

Google Chrome versions before 148.0.7778.96 contain a sandbox escape vulnerability in the Skia graphics library that allows attackers with initial renderer process access to achieve OS-level code…. A patch is available.

How to fix or mitigate CVE-2026-7923?

Within 24 hours: Verify current Chrome version across endpoints via MDM/inventory tools and communicate mandatory update requirement to all users. Within 7 days: Deploy Chrome 148.0.7778.96 or later via software management to all devices; prioritize endpoints handling sensitive data or high-value targets. Within 30 days: Confirm 100% deployment completion through vulnerability scanning and verify no instances of Chrome versions prior to 148.0.7778.96 remain in use.

Google Chrome CVE-2026-7923

EUVD-2026-27949 HIGH

Out-of-bounds Write (CWE-787)

2026-05-06 Chrome

Google Memory Corruption Buffer Overflow Red Hat Suse Chrome

8.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.3 HIGH

AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

SUSE

HIGH

qualitative

Red Hat

9.0 HIGH

qualitative

Primary rating from NVD.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

May 06, 2026 - 22:27 vuln.today

CVSS changed

May 06, 2026 - 22:22 NVD

8.3 (HIGH)

CVE Published

May 06, 2026 - 18:12 nvd

HIGH 8.3

DescriptionCVE.org

Out of bounds write in Skia in Google Chrome prior to 148.0.7778.96 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

AnalysisAI

Renderer sandbox escape in Google Chrome versions prior to 148.0.7778.96 leverages an out-of-bounds write in the Skia graphics library. An attacker who has already compromised Chrome's renderer process through other means (such as a separate browser vulnerability) can deliver a specially crafted HTML page to break out of Chrome's security sandbox, gaining elevated code execution on the underlying operating system. EPSS data not available; no CISA KEV listing identified. Google has released Chrome 148.0.7778.96 addressing this high-severity flaw, classified as CWE-787 (Out-of-bounds Write) affecting the Skia graphics rendering engine.

Technical ContextAI

Skia is Chrome's open-source 2D graphics library responsible for rendering text, shapes, and images across all platforms. This CWE-787 out-of-bounds write vulnerability allows memory corruption when processing malicious rendering instructions embedded in HTML/CSS. The CVSS vector's Scope:Changed (S:C) metric specifically indicates sandbox escape capability - the vulnerability crosses a security boundary from the sandboxed renderer process into a higher-privilege context. Chrome's multi-process architecture isolates web content rendering in low-privilege processes; successful exploitation breaks this critical security boundary. The attack complexity is rated High (AC:H) because it requires the attacker to have already achieved renderer compromise as a prerequisite, making this a second-stage exploitation primitive rather than an initial access vector.

RemediationAI

Update Google Chrome to version 148.0.7778.96 or later immediately via chrome://settings/help or allow automatic updates to apply. Official patch announcement at chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop.html confirms fix deployment. For enterprise environments using managed Chrome deployments, push version 148.0.7778.96 through administrative update channels and verify deployment via chrome://policy. If immediate patching is infeasible, implement defense-in-depth controls: enforce Chrome's site isolation feature via chrome://flags/#enable-site-per-process (enabled by default in recent versions but verify enforcement), restrict browser access to untrusted websites through network egress filtering or web proxy policies, and consider application sandboxing solutions like Windows Defender Application Guard for high-risk users. Note these mitigations do not eliminate the vulnerability but raise the bar for successful exploitation by limiting renderer compromise opportunities and adding additional isolation layers beyond Chrome's native sandbox.