Live data from Hacker News

Zero-day CSS: CVE-2026-2441 exists in the wild

chromereleases.googleblog.com

41–50 of 242 posts

Re: Zero-day CSS: CVE-2026-2441 exists in the wild

#41
post #9
post #5

"Google Chromium CSS contains a use-after-free vulnerability that could allow a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera." That's pretty bad! I wonder what kind of bounty went to the researcher.

So basically Firefox is not affected ?

The listed browsers are basically skins on top of the same chromium base.

It’s why Firefox and Safari as so important despite HN’a wish they’d go away.

Re: Zero-day CSS: CVE-2026-2441 exists in the wild

#42

Earlier quoted context omitted.

I think a big part of "criminally low" is that you'll make much more money selling it on the black market than getting the bounty.

I am far from the halls of corporate decision making, but I really don't understand why bug bounties at trillion dollar companies are so low.

Because it's nice to get $10k legally + public credit than it is to get $100k while risking arrest + prison time, getting scammed, or selling your exploit to someone that uses it to ransom a children's hospital?

Re: Zero-day CSS: CVE-2026-2441 exists in the wild

#43
post #9
post #5

"Google Chromium CSS contains a use-after-free vulnerability that could allow a remote attacker to potentially exploit heap corruption via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera." That's pretty bad! I wonder what kind of bounty went to the researcher.

So basically Firefox is not affected ?

Firefox is safe from this because their CSS handling was the first thing they rewrote in Rust.

Re: Zero-day CSS: CVE-2026-2441 exists in the wild

#45
post #9

Earlier quoted context omitted.

So basically Firefox is not affected ?

It's pretty hard to have an accidental a use after free in the FireFox CSS engine because it is mostly safe Rust. It's possible, but very unlikely.

Firefox and Safari developers dared the Chromium team to implement :has() and Houdini and this is the result!

/s

Re: Zero-day CSS: CVE-2026-2441 exists in the wild

#46

Devtools is seemingly partially broken in this version, if I have devtools open on a reasonably dynamic web app Chrome will crash within a minute or two

It's also been ridiculously slow for a month or two now :/ not a good time to be working on some relatively intricate performance optimisation with DevTools taking 1-4 seconds to even start the performance recording.

Re: Zero-day CSS: CVE-2026-2441 exists in the wild

#47

Earlier quoted context omitted.

It was intended as a joke reference to the 2004 Kerry / Bush debate. It's not a coincidence that Google would leave off an ad-blocking variant of Chrome.

they listed the top 3 most popular chromium browsers, covering 90%+ of chromium users

But not 90% of users here.

Re: Zero-day CSS: CVE-2026-2441 exists in the wild

#48
post #32

Earlier quoted context omitted.

I think a big part of "criminally low" is that you'll make much more money selling it on the black market than getting the bounty.

I read this often, and I guess it could be true, but those kinds of transaction would presumably go through DNM / forums like BF and the like. Which means crypto, and full anonymity. So either the buyer trusts the seller to deliver, or the seller trusts the buyer to pay. And once you reveal the particulars of a flaw, nothing prevents the buyer from running away (this actually also occurs regularly on legal, genuine b…

> Even revealing enough details, but not everything, about the flaw to convince a potential buyer would be detrimental to the seller, as the level of details required to convince would likely massively simplify the work of the buyer should they decide to try and find the flaw themselves instead of buying.

Is conning a seller really worth it for a potential buyer? Details will help an expert find the flaw, but it still takes lots of work, and there is the risk of not finding it (and the seller will be careful next time).

> And I imagine much of those potential buyers would be state actors or organized criminal groups, both of which do have researchers in house.

They also have the money to just buy an exploit.

> The real money to be made as a criminal alternative, I think, would be to exploit the flaw yourself on real life targets. For example to drop ransomware payloads; these days ransomware groups even offer franchises - they'll take, say, 15% of the ransom cut and provide assistance with laundering/exploiting the target/etc; and claim your infection in the name of their group.

I'd imagine the skills needed to get paid from ransomware victims without getting caught to be very different from the skills needed to find a vulnerability.

Re: Zero-day CSS: CVE-2026-2441 exists in the wild

#49
post #8

Earlier quoted context omitted.

I quoted directly from NIST, there's many other browsers and non-browsers that use chromium

It was intended as a joke reference to the 2004 Kerry / Bush debate. It's not a coincidence that Google would leave off an ad-blocking variant of Chrome.

did you also take poland being omitted to be some sort of conspiracy? seems you missed the point of why that "Actually, you forgot..." moment became such a punchline. Like it or not Brave is a very niche browser with rather insignificant market share why you would expect them to be mentioned in the first place is entirely lost on me. there are dozens of chromium forks also with under 1% market share, should we be forced to mention them all?

Re: Zero-day CSS: CVE-2026-2441 exists in the wild

#50
post #42

Earlier quoted context omitted.

I am far from the halls of corporate decision making, but I really don't understand why bug bounties at trillion dollar companies are so low.

Because it's nice to get $10k legally + public credit than it is to get $100k while risking arrest + prison time, getting scammed, or selling your exploit to someone that uses it to ransom a children's hospital?

Is it in fact illegal to sell a zero day exploit of an open source application or library to whoever I want?
Post reply on HN