Forever Security: browsers embedded in five AI coding assistants let web pages reach the host; Codex and VS Code still unpatched
READ THE ORIGINAL SOURCEOpen original sourceforever.security · Opens in a new tabForever Security reports that browsers embedded in five AI coding assistants (Cursor, GitHub Copilot, Codex, VS Code, Claude Desktop) let web pages or local files reach the host computer. Findings include arbitrary code execution, local file read and exfiltration, and address bar spoofing. The authors attribute the issues to a shared root cause they call EMBRACE, where embedded browsers are trusted like standalone ones. Codex and VS Code issues were unpatched at publication.
⚑ Review needed · why this is flagged
The automatic check found a question that still needs a human reading of the original source. The discovery rationale is not a verified finding.
The signal remains in the tracker so you can inspect its original source and discovery trail. This flag lowers its source evidence score; it does not judge whether the claim is true.
One primary source; other links are context, not independent corroboration.
- Primary sourcePrimary source discovery · source check open
- Linked in sourcethe technical companion
- Linked in sourceforever.security
Grok Bot submitted this discovery. The automatic check found a question that still needs a human reading of the original source. The discovery rationale is not a verified finding. The original source and submitted evidence remain inspectable; no editor has verified the claim.
Open full article view →- Linked article+30
- Fetched source page+30
- No editor link review+0
- Original non-discussion link+5
- Review needed-8
This measures the stored source trail and editorial steps. It does not certify accuracy, peer review, or independent corroboration. Popularity adds no points.
View full scoring →Read the scoring rubric →What the source says
Forever Security reports that browsers embedded in five AI coding assistants (Cursor, GitHub Copilot, Codex, VS Code, Claude Desktop) let web pages or local files reach the host computer. Findings include arbitrary code execution, local file read and exfiltration, and address bar spoofing. The authors attribute the issues to a shared root cause they call EMBRACE, where embedded browsers are trusted like standalone ones. Codex and VS Code issues were unpatched at publication.
A READER'S EVIDENCE CHECKHow to read this signalSix questions about claims, sources, risks, and open checks
This is a signal-level guide until claim-level evidence is available. “Not recorded” means the evidence has not been assessed here; it does not mean a result is false. How we check AI news →
- 01Who is making each claim?
The claimant and whether each claim was measured or asserted are not recorded in this public brief.
- 02What was actually tested?
Not recorded per claim. Check the source for sample size, tasks, model and benchmark versions, and reproducibility.
- 03Where are the sources?
Original link: forever.security. Brief basis: fetched source page. Primary page date and quote locations are not established in this panel.
- 04What could mislead?
The automatic check found a question that still needs a human reading of the original source. The discovery rationale is not a verified finding.
- 05What is at risk if wrong?
Not assessed per claim. Consider safety, privacy, cost, and adoption decisions before relying on the result.
- 06What would change the view?
No claim-specific check is recorded. An inspectable primary method or independent replication could change the assessment.
Key findings from the stored brief
- Cursor's embedded browser let a hidden page instruction lead the agent to run a command on the host.
- Claude Desktop and VS Code restricted local pages to their project folder, but a web worker could read files across the disk.
- Codex reportedly let a local page read any file on the machine directly.
- GitHub Copilot's browser preview accepted page-supplied addresses, so the address bar could show a site the tab was not on.
Source claims not independently checked; the findings are the vendor's own and the Codex and VS Code issues were unpatched at publication.
This is a source-based abstract, not independent validation of the source's claims.
Evidence & sources
These links show where the signal came from and what the source page linked to. A linked page is context, not independent corroboration.
Related archive coverage
These relationships record a citation or topic overlap, not confirmation of the finding.
Grok Bot submitted this discovery. The automatic check found a question that still needs a human reading of the original source. The discovery rationale is not a verified finding. The original source and submitted evidence remain inspectable; no editor has verified the claim.
These are Grok Bot discovery notes. AINewsIQ prepared a brief from available source material. The bot's rationale, linked posts, authors, and stances have not been independently verified.
Security firm Forever Security says it found code execution, local file reads, prompt injection and address-bar spoofing in the browsers embedded in five AI coding assistants, all from one root cause it calls EMBRACE: an embedded browser given extra powers. It says the Codex and VS Code issues are unpatched at publication. Findings are the firm's own; vendors' responses are not in the post.
Source claims not independently checked; the findings are the vendor's own and the Codex and VS Code issues were unpatched at publication.
Engagement counts, when shown, are observed snapshots. They do not establish accuracy or corroboration.
Timeline & updates
- Signal dated by source or discovery feed
This timestamp places the signal in the radar. It may be the discovery post date rather than the primary page's first publication date.
- Shared brief stored
AINewsIQ prepared one abstract from fetched source page.
A publication revision history is not stored for this signal. New engagement snapshots do not mean the source itself changed.
Why this may matter
Developers commonly run these assistants on endpoints holding SSH keys, cloud credentials, and source code. If embedded browsers inherit weaker isolation than standalone browsers, a single opened file or visited page could expose sensitive data, and some issues remained unpatched at publication.
Limits and open questions
Source claims not independently checked; the findings are the vendor's own and the Codex and VS Code issues were unpatched at publication.
Organization-specific financial, security, and operational effects require the organization's own context and review.
Discussion
Comments are reviewed before publication. Discuss the evidence, not the person.
No published comments yet.
Reader discussion opens with accounts. You can read the original source and published comments now.