EUVD-2026-35230
GHSA-72h3-r85p-88m3
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Use after free in File Input in Google Chrome prior to 149.0.7827.103 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)
AnalysisAI
Heap corruption in Google Chrome's File Input component before version 149.0.7827.103 allows a remote attacker to exploit a use-after-free condition by luring a user to a crafted HTML page, with Chromium rating the issue Critical. No public exploit identified at time of analysis, but the high CVSS 8.8 score and browser attack surface make this a priority patch for desktop fleets.
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 | The victim must browse to attacker-controlled or attacker-influenced HTML using a Chrome desktop build older than 149.0.7827.103, and must reach a code path that exercises the File Input component (a page that scripts or renders an <input type="file"> element in the vulnerable manner). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H reflects a network-reachable, low-complexity, unauthenticated bug whose only meaningful barrier is required user interaction (visiting a malicious page), yielding a base score of 8.8. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts a crafted HTML page that scripts the file-input element to trigger the use-after-free, then delivers it via phishing, malvertising, or a watering-hole compromise. When a victim visits the page in a vulnerable Chrome build, the heap corruption is triggered inside the renderer process, giving the attacker a memory-corruption primitive that can be developed into code execution within the sandbox - and, if chained with a sandbox-escape bug, into full system compromise. … |
| Remediation | Vendor-released patch: Google Chrome 149.0.7827.103 (Stable channel) - upgrade all desktop installations immediately via the built-in updater or managed deployment tooling, then force a browser restart so the new binaries are loaded. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: Issue security alert to all users; audit current Chrome versions across the desktop fleet to identify unpatched systems. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Vendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today