>>947589 (OP)
There is simply none. Web browsers are exclusively bloated products. Bloated doesn't even begin to describe it. They should be called "hyperbloated" or something. There isn't a single real software engineer touching any web browser right now. Links would be your best bet but it isn't exactly user friendly, and lots of sites break with it. I've tried like 10 browsers and they're all shit the moment you look at them. But most of the issues come from the "engine". If a web browser is using a known "web engine", you already know it's complete garbage. You could make a simple wrapper around the engine, and it will still be bloated as fuck.
Also, I'm talking about RCE attacks. Making an RCE-free web browser would be trivial, just don't use C and don't use eval or whatever meme construct your non-C language has.
If you're talking about avoiding attacks on websites that pretend to be applications, such as CSRF, XSS, clickjacking, etc, it's not even possible to solve those problems. They stem from the shitty protocol. They are introduced by both the browser developer and the "web application" developer. But nobody sane uses the web for anything other than browsing documents anyway so that is a non-problem.