Skip to main content

Google EUVDEUVD-2026-13461

| CVE-2026-4447 HIGH
Protection Mechanism Failure (CWE-693)
2026-03-20 chrome-cve-admin@google.com
8.8
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft malicious HTML page
  2. Delivery
    Send to target user
  3. Exploit
    User visits page in Chrome
  4. Execution
    V8 parser processes crafted content
  5. Persist
    Sandbox escape triggered
  6. Impact
    Arbitrary code executes in sandbox

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Protection mechanism completeness
Exploitation Conditions

The victim must open a crafted HTML page in Google Chrome versions prior to 146.0.7680.153. Remote unauthenticated attacker can deliver the malicious HTML via email, website, or messaging. No special Chrome configuration required.

Impact

Despite the absence of CVSS score and EPSS data in the provided metadata, this vulnerability presents critical real-world risk for several reasons: (1) the attack vector is network-based with low complexity (crafted HTML), (2) exploitation results in arbitrary code execution within a sandboxed process, (3) Google assigned 'High' severity classification indicating internal risk assessment supports criticality, (4) a patch is available from the vendor indicating the issue was substantiated, and (5) the EUVD tracking and Debian distribution flags indicate widespread impact across enterprise and consumer deployments. The absence of KEV status and POC information in provided data does not diminish risk—this is a recent CVE (2026) with limited public disclosure timeline. Organizations should treat this as high-priority based on the sandbox escape capability and network attack surface, regardless of CVSS numerical scores.

Exploit ScenarioDerived

An attacker crafts a malicious HTML page containing specially crafted JavaScript code that triggers a flaw in V8's JIT compilation or memory management. When a victim user visits this page via Chrome prior to 146.0.7680.153, the crafted JavaScript executes and exploits the sandbox boundary violation, allowing the attacker's code to break out of the sandbox isolation layer and execute arbitrary code with the privileges of the Chrome renderer process. This could lead to data theft, malware installation, or lateral movement to the host system depending on the exploit sophistication.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 20, 2026

A sandbox escape vulnerability exists in Google Chrome's V8 JavaScript engine prior to version 146.0.7680.153, allowing remote attackers to execute arbitrary code within the Chrome sandbox through a crafted HTML page. This is a High severity issue affecting millions of Chrome users across Windows, macOS, and Linux platforms. The vulnerability is triggered via web-based attack vector (HTML page delivery) and does not require user interaction beyond visiting a malicious website.

RemediationAI

Immediately upgrade Google Chrome to version 146.0.7680.153 or later. For enterprise deployments, use Chrome's built-in auto-update mechanism or deploy the patched version through centralized device management (MDM/EMM). Debian users should update chromium-browser packages through their distribution repositories. No workarounds can reliably mitigate sandbox escape vulnerabilities prior to patching—if immediate patching is delayed, consider restricting access to untrusted web content by disabling Chrome on high-risk user accounts or using enhanced sandboxing features if available in your Chrome version. Verify patching completion by checking chrome://version to confirm running build 146.0.7680.153 or higher. Refer to https://chromereleases.googleblog.com/2026/03/stable-channel-update-for-desktop_18.html for detailed release notes and patch deployment guidance.

Affected VersionsENISA

Chrome 146.0.7680.153 <146.0.7680.153

Affected Packages

euvd chrome fix: 146.0.7680.153

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability resides in V8, Google's open-source JavaScript engine that powers Google Chrome and Chromium-based browsers. V8 implements a Just-In-Time (JIT) compiler and garbage collector for JavaScript execution. The 'inappropriate implementation' described in the CVE indicates a logic flaw in V8's sandboxing mechanisms or memory safety guarantees, likely related to how the engine handles specific JavaScript constructs or edge cases. The vulnerability affects Chrome versions prior to 146.0.7680.153 across all desktop platforms. While no CWE is formally assigned in the available metadata, sandbox escape vulnerabilities typically stem from memory corruption (CWE-119), type confusion (CWE-843), or improper validation of security boundaries (CWE-693).

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Ubuntu MEDIUM
SUSE HIGH
Red Hat 9.6 HIGH

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch released
Mar 20, 2026 - 08:46 nvd
Patch available
CVE Published
Mar 20, 2026 - 02:16 nvd
HIGH 8.8

DescriptionNVD

Inappropriate implementation in V8 in Google Chrome prior to 146.0.7680.153 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)

Executive ViewAI

Why It Matters

Organizations using V8 in Google Chrome face significant risk from CVE-2026-4447 rated CVSS 8.8. Successful exploitation could significantly impact the confidentiality, integrity, or availability of affected systems. A patch is available and should be applied as part of regular vulnerability management.

Business Impact: Severe
Compensating Controls

Apply vendor patch. If immediate patching is not feasible: (1) Implement network-level access controls to limit exposure; (2) Enable enhanced monitoring and alerting; (3) Apply principle of least privilege.

Threat Intelligence Overview

EPSS Score
0.0%
Top 89% exploitable
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment Vendor VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Vendor StatusVendor

Ubuntu

Priority: Medium
chromium-browser
Release Status Version
jammy not-affected code not present
noble not-affected code not present
questing not-affected code not present
upstream released -

Debian

chromium
Release Status Fixed Version Urgency
bullseye (security), bullseye vulnerable 120.0.6099.224-1~deb11u1 -
bookworm fixed 146.0.7680.153-1~deb12u1 -
bookworm (security) fixed 146.0.7680.153-1~deb12u1 -
trixie fixed 146.0.7680.153-1~deb13u1 -
trixie (security) fixed 146.0.7680.153-1~deb13u1 -
forky vulnerable 146.0.7680.80-1 -
sid fixed 146.0.7680.153-1 -
bullseye fixed (unfixed) end-of-life
(unstable) fixed 146.0.7680.153-1 -

SUSE

Severity: High
Product Status
SUSE Package Hub 15 SP6 Fixed
openSUSE Leap 15.6 Fixed
openSUSE Leap 16.0 Fixed
openSUSE Tumbleweed Fixed
SUSE Package Hub 15 SP6 Fixed

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy