The little browser inside your coding assistant is still a browser, and it can still be talked into doing too much. The Injection reports that Forever Security, on October 29, 2026, described a class of flaws it calls EMBRACE in “the browsers embedded in Cursor, GitHub Copilot, Codex, VS Code and Claude Desktop.” According to that summary, “a page or local file can read files across the disk or run code.” At the time of the report, “Codex and VS Code are unpatched.”
Quick Take
- What: EMBRACE, a shared failure class in embedded (Electron-style or similarly hosted) browsers used by five widely deployed AI assistants and editors.
- Impact: A malicious page or a local file loaded in that browser could read files elsewhere on the machine, or run code.
- Patch status as of October 29: Codex and VS Code were still unpatched, per The Injection’s summary of Forever Security. Other vendors in the set may have shipped fixes; check each product’s release notes rather than assuming a single patch date.
- Until a fix: Do not let these assistants open untrusted HTML, local preview files, or arbitrary URLs in their built-in browsers.
What happened
AI coding tools increasingly preview web apps, render model-generated HTML, and open documentation inside an embedded browser instead of the user’s Chrome or Safari window. That inner browser often has a weaker security model, or extra bridges back into the host application, because it is supposed to be “just a preview.” EMBRACE is Forever Security’s name for what happens when that assumption fails: a page, or even a local file, can reach beyond the preview and read the disk or execute code.
i10x has not reproduced the primitives, and The Injection’s week-44 note does not list CVE numbers for every affected app. The operational message is the cross-product scope — five assistants, one pattern — and the explicit statement that two of them were still unpatched on October 29.
What you should do
- Update Cursor, GitHub Copilot, Codex, VS Code and Claude Desktop to the latest versions and read the vendor notes for EMBRACE or embedded-browser fixes.
- If you run Codex or VS Code and cannot confirm a fix, treat in-app previews of untrusted HTML as unsafe. Prefer an external, locked-down browser for unfamiliar links.
- Do not open untrusted local HTML files or model-generated preview pages in the assistant’s embedded browser until your vendor has patched.
What it means
This is a cousin of classical Electron issues, now sitting in the tools that also have access to your repo and your cloud credentials. A file-read from a preview pane is already a secret-leak path; combined with an agent that will happily follow a link in a README, it becomes a realistic attack. The unfinished patches on Codex and VS Code, if they remain open, are the urgent part of an already urgent class.
About the analysis
Researched and written with AI assistance under the editorial responsibility of the i10X News team. The title image is an AI-generated illustration. Read our AI Use Policy. Spotted an error? Request a correction.
This i10x report is based on The Injection’s week-44 summary of Forever Security’s October 29, 2026 EMBRACE report. i10x did not test the five applications and has not independently verified later patches after that date.
