EUVD-2026-66068
GHSA-rw6j-f47w-3gqj
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
In-sandbox out-of-bounds read yields confidentiality impact only; no integrity or availability impact, and S:U confirms no sandbox escape.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Integer overflow in Chromium in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to read memory inside the sandbox via a crafted file. (Chromium security severity: Low)
AnalysisAI
Integer overflow (CWE-190) in Chromium's file-processing code exposes all desktop Google Chrome versions prior to 152.0.7977.65 to in-sandbox memory disclosure when a user opens a specially crafted file, requiring no authentication (PR:N) but requiring user interaction (UI:R). A critical data conflict across sources warrants attention: the NVD CVSS score is 8.8 with C:H/I:H/A:H, yet Google's Chromium team rates this Low severity, and the EPSS is 0.16% (5th percentile) with SSVC Exploitation:none - collectively suggesting the attack impact is bounded to memory readable within the sandboxed renderer, without sandbox escape. …
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 the victim to open a specially crafted file in Google Chrome - CVSS UI:R confirms this active user-interaction prerequisite, meaning drive-by exploitation without file-open interaction is not indicated. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Multiple intelligence signals conflict in this case, and the discrepancy itself is the most important risk signal. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker crafts a malicious file containing integer values designed to overflow a size or length field in a Chromium file-format parser. The file is delivered to the target - via a malicious web page, email attachment, or shared document - and the victim opens it in Chrome, triggering the integer overflow in the sandboxed renderer process and enabling an out-of-bounds memory read. … |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later - this is the vendor-confirmed fix version per the stable channel advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: notify all Chrome users and IT staff of the vulnerability and direct them to 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-190 – Integer Overflow or Wraparound
View allSame technique Integer Overflow
View allShare
External POC / Exploit Code
Leaving vuln.today