Sandboxed code execution via malicious file
Published Jun 30, 2026 · Updated Jun 30, 2026
Improper input validation in Google Chrome for iOS before 150.0.7871.47 allows local users to execute code inside its sandbox via a malicious file. Public records do not disclose the affected parser, file format, or incorrect validation operation because the linked Chromium issue is restricted. Processing a malicious file on iOS and user interaction are required, and the resulting code execution remains inside the browser sandbox.
Summary
What happened
Improper input validation in Google Chrome for iOS before 150.0.7871.47 allows local users to execute code inside its sandbox via a malicious file. Public records do not disclose the affected parser, file format, or incorrect validation operation because the linked Chromium issue is restricted. Processing a malicious file on iOS and user interaction are required, and the resulting code execution remains inside the browser sandbox.
The record
- CVE
- CVE-2026-13850
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- Go standard library
- Product
- Google Chrome
- Classifications
- CWE-20, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 2026CVE publishedPublication date reported by the CVE source.
- Jun 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=150.0.7871.47 <150.0.7871.47
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo