AIToday
AI Coding AssistantsAI Safety & AlignmentHacker NewsPublished: Oct 31, 2026, 13:00 JST

EMBRACE: five AI coding tools' browsers broke basic rules

Send on LINE
EMBRACE: five AI coding tools' browsers broke basic rules

3 Key Points

  1. What happened

    Forever Security's EMBRACE research found Cursor's browser let any page send text into the agent's composer, Codex and VS Code previews could read files outside the project, and the GitHub Copilot app could fake its address bar.

  2. Why it matters

    The researchers' testing indicates a page or local file could trigger unintended actions inside the agent, potentially exposing secrets on a developer's machine; they call the Cursor attack probabilistic across models.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

Forever Security's Gal Weizman grouped the findings under EMBRACE, for an embedded browser trusted like a real one, after testing how the preview browsers in five AI coding tools handled powers a normal browser never grants. The write-up walks through each product's failure separately: Cursor exposed an object called window.cursorBrowser.send to every site, and the researchers split a command across hidden attributes so the agent would not refuse it. Codex's preview returned the contents of a file:// path on a plain fetch, while VS Code and Claude Desktop checked only the main page and not the web workers a page can start. The GitHub Copilot app, built on the Tauri framework, let a page report any address as its own.

The delivery path the researchers describe starts with a project the user is willing to open. A README can lead the assistant to write a clickable file:// link to a booby-trapped page, and clicking it runs the page. Microsoft and Anthropic first answered with Workspace Trust, but Weizman told Help Net Security that the prompt gives the user no protection here, because opening the project was already the user's choice. The write-up positions its grep search as triage signals rather than proof, noting that benign code can match some strings.

Patch status varies across the five. Cursor was fixed on October 1 and the GitHub Copilot app in 1.1.29 on October 13, while Codex and VS Code remained unpatched as of October 29, 2026. Anthropic declined Forever's report but accepted a separate Noma Security report as valid, and the write-up states no fixed version for Claude Desktop. The researchers also note that the Cursor attack's success depends on the model and is not certain every time.

FAQ
Which of the five tools are still unpatched?
Codex and VS Code were unpatched as of October 29, 2026, per the researchers. Claude Desktop's fix status is unclear because Anthropic declined Forever's report but accepted a separate Noma Security report.
How did the GitHub Copilot app issue get fixed?
GitHub fixed it on its own in version 1.1.29 on October 13, before a report was filed, according to the researchers. The flaw let a page call a Tauri command to display a fake address bar.
What can Cursor users do to block the one-keystroke path?
Turning off auto-run or keeping a short allowlist also blocks the one-keystroke path, the write-up says. Cursor itself was patched on October 1, per the researchers.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articlePowerlattice sells $86,009,965 of $111,010,000 equity offering