Live data from Hacker News

Actively exploited sandbox RCE in all Chromium versions

nvd.nist.gov

41–50 of 518 posts

Re: Actively exploited sandbox RCE in all Chromium versions

#41
post #31
post #22

Earlier quoted context omitted.

Which browser has a better security track record?

Firefox with uBlock Origin. It’s astonishing how many exploits uBO stops before they ever reach your browser engine. It’s the antivirus of the 2020s.

I suggest Zen browser (fork of FF), it feels closer to chrome.

Re: Actively exploited sandbox RCE in all Chromium versions

#42
post #32

Earlier quoted context omitted.

Seems to use OS-specific kernel syscall filtering facilities. Windows: https://chromium.googlesource.com/chromium/src/+/HEAD/docs/d... Linux: https://chromium.googlesource.com/chromium/src/+/0e94f26e8/d...

V8 also has its own sandbox, which I believe exists in that sandbox. I assume that's the one this exploit has RCE in, but its unclear. https://chromium.googlesource.com/v8/v8.git/+/refs/heads/mai...

I would assume in this case that there's full renderer control, not just a bypass of the in-process isolation.

Re: Actively exploited sandbox RCE in all Chromium versions

#43
post #23
post #7

Earlier quoted context omitted.

It means it can execute arbitrary machine code in the sandbox.

Okay, and why is that more of a security risk than executing arbitrary JavaScript in the sandbox?

Because Javascript theoretically can't just access files on disk. Control over the render would let you do that, if not for the process level sandbox, which constraints things like file access, system, calls, etc.

But the process is still more capable than the VM. The process can talk to other processes via IPC, for example.

That's why you don't go from "javascript -> computer is taken over", instead you go from "javascript -> renderer control -> computer is taken over".

Re: Actively exploited sandbox RCE in all Chromium versions

#44
post #31

Earlier quoted context omitted.

Firefox with uBlock Origin. It’s astonishing how many exploits uBO stops before they ever reach your browser engine. It’s the antivirus of the 2020s.

I suggest Zen browser (fork of FF), it feels closer to chrome.

In a good way?

Re: Actively exploited sandbox RCE in all Chromium versions

#45

Let's take a moment to talk about the monetary value of this vulnerability. According to the Chrome release page ( https://chromereleases.googleblog.com/2026/09/stable-channel... ), Google paid a researcher $1000 for ethically reporting this. The CVE associated with it (CVE-2026-85046) is already being exploited in the wild. If we put our thinking caps on, how much do you think this vulnerability is actually worth? H…

While I agree 1000 is hilariously low for this, worth is hard to quantify. Do you pay what it could theoretically cost your company? the amount the top bidding bad actor would be willing to pay?

You let the market decide. Google could purchase the bugs on the same market blackhats do.

Re: Actively exploited sandbox RCE in all Chromium versions

#46

Just one more reason to never use Chrome. Their removal of MV2 to prevent UBlock Origin from working is another.

Chrome product management is horrible. Chrome software engineering is some of the best ever done.

(And no, I don't use it except for testing).

Re: Actively exploited sandbox RCE in all Chromium versions

#47
post #6
post #3

Earlier quoted context omitted.

RCE inside sandbox, so requires chaining with another 0day.

What exactly does "RCE inside sandbox" describe that goes beyond "the webpage can supply arbitrary JavaScript and the JavaScript engine executes it", but is still isolated from the system?

Chrome runs webpages in individual sandbox processes with very low privileges, as a defense-in-depth strategy. It generally requires at least two exploits to actually affect a user--first, get RCE in a sandboxed process, then find a separate vulnerability that lets you escape the sandbox process entirely. For this bug to have actually been used in the wild, there was almost certainly a second bug as well.

Re: Actively exploited sandbox RCE in all Chromium versions

#49
post #7
post #6

Earlier quoted context omitted.

What exactly does "RCE inside sandbox" describe that goes beyond "the webpage can supply arbitrary JavaScript and the JavaScript engine executes it", but is still isolated from the system?

It means it can execute arbitrary machine code in the sandbox.

> It means it can execute arbitrary machine code in the sandbox.

Well which is precisely why we have sandboxes.

To me "executing arbitrary code in the sandbox" is similar to "I don't give a flying fuck for it's what a sandbox is for".

More information is needed. As someone commented: this has to be paired with at least another exploit to make anything remotely useful.

A sandbox is a sandbox. We want to understand how "code running in a sandbox" is "actively exploited".

Re: Actively exploited sandbox RCE in all Chromium versions

#50

Just one more reason to never use Chrome. Their removal of MV2 to prevent UBlock Origin from working is another.

Chrome product management is horrible. Chrome software engineering is some of the best ever done. (And no, I don't use it except for testing).

I don’t disagree, two or more things can be true at once.

That said I still use Firefox for other reasons.

I simply don’t trust google, I don’t trust Mozilla either but I do trust them more than Google and you do kinda have to have a browser to function in the modern world.

Post reply on HN