logoalt Hacker News

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

151 pointsby idoxertoday at 4:28 PM79 commentsview on HN

Comments

mpegtoday at 4:51 PM

"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.

show 5 replies
kykattoday at 7:37 PM

I don't quite understand the vulnerability, when exploited, you can get information about the page from which the exploit code is running. Without a sandbox escape or XSS, that seems almost completely harmless?

This is the "impact" section on https://github.com/huseyinstif/CVE-2026-2441-PoC:

Arbitrary code execution within the renderer process sandbox Information disclosure — leak V8 heap pointers (ASLR bypass), read renderer memory contents Credential theft — read document.cookie, localStorage, sessionStorage, form input values Session hijacking — steal session tokens, exfiltrate via fetch() / WebSocket / sendBeacon() DOM manipulation — inject phishing forms, modify page content Keylogging — capture all keystrokes via addEventListener('keydown')

show 1 reply
tripplyonstoday at 4:49 PM

"Use after free in CSS" is a funny description to see.

show 2 replies
himata4113today at 5:00 PM

The fact that these still show up is pretty wild to me. Don't we have a bunch of tools that should create memory-safish binaries by applying the same validation checks that memory-safe languages get for free purely from their design?

I get that css has changed a lot over the years with variables, scopes and adopting things from less/sass/coffee, but people use no-script for the reason because javascript is risky, but what if css can be just as risky... time to also have no-style?

Honestly, pretty excited for the full report since it's either stupid as hell or a multi-step attack chain.

show 1 reply
agentifyshtoday at 7:21 PM

this is insane! what other zero days are out there and being used

also this seems chromium only so it doesnt impact firefox ?

ripbozotoday at 5:48 PM

I'd love to see what the PoC code looks like, of course after the patch has been rolled out for a few weeks.

show 1 reply
bitbashertoday at 5:27 PM

Maybe Chromium should also rewrite their rendering engine in Rust ;p

jijjitoday at 7:14 PM

use after free.... ahh the irony

astrobe_today at 5:41 PM

This doesn't affect the many browsers based on Chromium?

show 2 replies
MallocVoidstartoday at 4:57 PM

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

show 1 reply
kittbuildstoday at 6:19 PM

[dead]

idoxertoday at 4:30 PM

[dead]

fulafeltoday at 5:05 PM

Isn't this a wrongly editorialized title - "Reported by Shaheen Fazim on 2026-02-11" so more like 7-day.

show 1 reply
baqtoday at 4:53 PM

I wonder if this was found with LLM assistance, if yes, with which one and is it a one-off or does it mark a start of a new era (I assume it does).

show 1 reply