News for hackers. Stuff that matters.
Re:NeoBrowser: An MCP server that drives real Chrome with yo... by dongkeren on Tuesday August 18, 2026 @11:33AM (#49347235)
I am wondering how it solves the security issues:

I saw opt-in, file permissions and SSRF in README, but I do not see:

domain allowlist; human approval before submiting/deleting; persistent audit record after operations; how to revoke a previously granted access;

The prompt injection may also induce the agent to perform write operations.

Reuse the real user-login session also delegate the user's full authority to the agent, which obviously has potential security issues.

The point is, the more real authority the agent has, the more important the responsibility the agent must take, which I think should be designed in from the beginning.

Re:NeoBrowser: An MCP server that drives real Chrome with yo... by hotelsacher on Tuesday August 18, 2026 @11:38AM (#49347309)
> I am wondering how it solves the security issues

I bet it doesn't. It's one gaping security hole.

Re:NeoBrowser: An MCP server that drives real Chrome with yo... by pitiflautico on Tuesday August 18, 2026 @03:14PM (#49351094)
Domain allowlist is in: NEOBROWSER_DOMAIN_ALLOWLIST=github.com,.docs.rs — navigate rejects anything not listed with an error that names the allowed hosts. Exact hosts or .suffix, opt-in (unset = no restriction). Appreciate the push on this one.