EUVD-2026-50836
GHSA-j6wg-9fv2-p5wc
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Raised to AC:H because a successful escape presupposes prior renderer compromise plus a crafted page; scope Changed as the sandbox boundary is crossed, with full C/I/A impact on the browser process.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
5DescriptionCVE.org
Inappropriate implementation in MHTML in Google Chrome on Mac prior to 151.0.7922.72 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
Sandbox escape in Google Chrome for macOS prior to 151.0.7922.72 lets an attacker who has already compromised the renderer process break out of the sandbox and reach the more-privileged browser process by loading a crafted HTML page that abuses Chrome's MHTML handling. It is rated High by Chromium and carries a CVSS 9.6 (scope-changed) score, but exploitation is a second-stage step that presupposes prior renderer compromise. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires that the attacker has ALREADY compromised the Chrome renderer process (per the description) and that the victim loads a crafted HTML/MHTML page in Chrome on macOS (CVSS UI:R). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The signals are deliberately mixed and should be weighed together. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first uses a separate renderer-compromise bug to gain code execution inside a Chrome tab's sandboxed renderer, then serves or references a crafted MHTML/HTML page that abuses the inappropriate MHTML implementation to escape the sandbox and execute in the higher-privileged browser process on macOS. No public exploit is identified at time of analysis, and CVSS AC:L suggests the escape step itself is not technically difficult once the renderer foothold and page load (UI:R) are in place. |
| Remediation | Vendor-released patch: upgrade Google Chrome on macOS to 151.0.7922.72 or later via the Stable Channel update (https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html); Chrome normally auto-updates, so ensure the browser is fully closed and relaunched to apply the new build, and confirm the version under chrome://settings/help. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, audit Chrome versions across all macOS endpoints using your asset management or MDM system and notify users of the available patch. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-693 – Protection Mechanism Failure
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today