Live data from Hacker News

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

chromereleases.googleblog.com

211–220 of 242 posts

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

#211
post #163

Earlier quoted context omitted.

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

Does the Rust implementation not use any unsafe and does not use libraries using unsafe?

No. What would be the point of that?

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

#212

Earlier quoted context omitted.

Maybe it's more complicated than that? With allocate/delete discipline, C can be fairly safe memory-wise (written a million lines of code in C). But automated package managers etc can bring in code under the covers, and you end up with something you didn't ask for. By that point of view, we reverse the conclusion.

yes, people often invoke "simply write safer c" but that doesn't make it any more realistic of a proposition in aggregate as we keep seeing.

Yet so many language features that 'help' with this issue, end up not helping. Null pointers are endemic in Java, as well as leaks. Heap fragmentation becomes difficult to address when the language hides it under layers of helpful abstraction.

In the end, discipline of some kind is needed. C is no different.

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

#213

Earlier quoted context omitted.

Chromium is pretty aggressively fuzzed. There aren't a lot of dark corners that can't be reached via a sufficiently aggressive fuzzer.

Not sure about that one. Fuzzers have a hard time creating certain narrow preconditions that a manual review can find.

They’ve gotten way better at this over the last decade with coverage guided execution.

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

#214
post #187

Earlier quoted context omitted.

HN wants Firefox but with better stewardship and fewer misdirected funds. Mozilla - wrongly - believes that the majority of FF users believe in Mozilla's hobby projects rather than that they care about their browser. That's why - as far as I know - to this day it is impossible to directly fund Firefox. They'd rather take money from google than to be focusing on the one thing that matters.

I just want Firefox's search box to be on the top of the window so I don't have to bend my neck when I'm surfing in bed... I don't use it just for that.

If you're talking about url/search bar at the bottom on mobile, that's customisable - actually they ask you which you prefer when you install it, but you can change it at any time in settings. (personally I prefer all that stuff at the bottom since it's more conveniently where all my other phone nav is, and visibility fits in well with how I scroll)

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

#215
post #211
post #163

Earlier quoted context omitted.

Does the Rust implementation not use any unsafe and does not use libraries using unsafe?

No. What would be the point of that?

Not Firefox, but Servo has quite a lot of unsafe, even though some of the results are false positives.

https://grep.app/search?f.repo=servo%2Fservo&f.repo.pattern=...

So Servo at the very least cannot be said to be 'safe'. And I believe the Rust code in Firefox is similar.

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

#216

Earlier quoted context omitted.

Not sure about that one. Fuzzers have a hard time creating certain narrow preconditions that a manual review can find.

They’ve gotten way better at this over the last decade with coverage guided execution.

Well, yes and no. For example, coverage-guided fuzzers won't reliably find the taken branch in

  if (hash(x) == 0x12345678) {

  }
Of course this is contrived, but you can imagine something similar where it requires a delicate setup for that branch to be taken at all, that a human (or these days, an LLM) can find straightforwardly.

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

#218
post #204

Earlier quoted context omitted.

[flagged]

I'll need you to be much more specific. I'm actually quite familiar with Rust, having worked with it since 2015, speaking at the first rustconf, having written in it professionally, having worked on a team that did vulnerability research with a highly hardened Rust codebase[0] in which `unsafe` usage introduced a vulnerability, etc. If you'd like me to construct a formal syllogism to communicate my points then I migh…

[flagged]

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

#219

Earlier quoted context omitted.

HN doesn't want firefox to go away. HN wants firefox to be better, more privacy/security focused, and to stop trying to copy chrome out of the misguided hope that being a poor imitation will somehow make it more popular. Sadly, mozilla is now an adtech company ( https://www.adexchanger.com/privacy/mozilla-acquires-anonym-... ) and by default firefox now collects your data to sell to advertisers. We can expect less an…

What would be an acceptable revenue model? Google Chrome has the same privacy profile with the exception that Google retains the data for their own ad platforms. Selling preferential search access is legally precarious due to FTC's lawsuit against Mozilla.

The biggest problem is a failure of trust. I won't donate to the Mozilla foundation because I have zero faith in them using that money wisely.

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

#220
post #218

Earlier quoted context omitted.

I'll need you to be much more specific. I'm actually quite familiar with Rust, having worked with it since 2015, speaking at the first rustconf, having written in it professionally, having worked on a team that did vulnerability research with a highly hardened Rust codebase[0] in which `unsafe` usage introduced a vulnerability, etc. If you'd like me to construct a formal syllogism to communicate my points then I migh…

[flagged]

[flagged]
Post reply on HN