---
id: "CVE-2026-118331"
kind: "vulnerability"
aliases: ["CVE-2026-118331"]
title: "Chrome: FileAPI input validation flaw lets crafted page run code"
severity: "critical"
cvss: null
epss: null
exploited: false
status: "open"
category: "runtime"
products: []
ecosystems: []
tags: ["browsers", "chrome", "desktop-fleet", "runtime"]
not_affected_if: ["chrome-156.0.8078.73-or-later"]
published_at: "2026-10-27T23:17:01+00:00"
first_seen_at: "2026-10-27T23:29:43+00:00"
updated_at: "2026-10-27T23:31:52+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-118331", "first_seen_at": "2026-10-27T23:29:43+00:00"}]
---

# Chrome: FileAPI input validation flaw lets crafted page run code

Google Chrome before 156.0.8078.73 mishandles input in its FileAPI, so a crafted HTML page can make the browser run attacker code inside the renderer sandbox. Chromium rates the flaw Critical.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `chrome://version` in Chrome and compare the version with `156.0.8078.73`
- On managed fleets, check the installed Chrome build with the endpoint management tool
- Chromium-based browsers (Edge, Brave) may need their own version check, which the sources do not say

## Fix

- Update Google Chrome to `156.0.8078.73` or later
- Restart the browser after the update so the new build is running
- Update other Chromium-based browsers when their vendors ship the fix, which the sources do not say

## Timeline

- 2026-10-27T23:29:43+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-118331

## From the sources

Improper input validation in FileAPI in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Critical)

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_