This discovery was around the same time this same researcher found another critical vulnerability in a different project that we cannot talk about yet due to the same concerns as nginx2root.
I expect at the point where five different places found at least some of the same issues, you have to assume that the moment the release is cut, people will figure out what the vulnerability is. Holding it any longer just means people might not realize the update is important on time.
(Also it does seem the releases have been published, so a patch is "available". It may not make it to your distro on time, but again, once the release is cut, it's effectively public already.)
sure, but even with AI and so on, surely it'd take would-be attackers at least a little time to develop a working exploit. doesn't it make sense to give the distros at least an hour or two to get this ready first?
I suppose because it’s relatively easy to prevent before patches are available (by disabling HTTP/2), making it a bit less of a race between updating and attackers reverse-engineering the vulnerability?
refi64 | an hour ago
Fun times lie ahead!
sigmonsez | 20 minutes ago
Is this just marketing for xint ?
My default install on ubuntu does not have http/2 enabled.
ggpsv | 39 minutes ago
As of the time of this writing, the Nginx version in Debian stable is vulnerable and no security advisories / updates are available.
rbca | 31 minutes ago
why on earth are they revealing all this information BEFORE the patch is available????
refi64 | 26 minutes ago
I expect at the point where five different places found at least some of the same issues, you have to assume that the moment the release is cut, people will figure out what the vulnerability is. Holding it any longer just means people might not realize the update is important on time.
(Also it does seem the releases have been published, so a patch is "available". It may not make it to your distro on time, but again, once the release is cut, it's effectively public already.)
rbca | 22 minutes ago
sure, but even with AI and so on, surely it'd take would-be attackers at least a little time to develop a working exploit. doesn't it make sense to give the distros at least an hour or two to get this ready first?
jamesnvc | 22 minutes ago
I suppose because it’s relatively easy to prevent before patches are available (by disabling HTTP/2), making it a bit less of a race between updating and attackers reverse-engineering the vulnerability?
cadey | 2 hours ago
Obligatory: https://xeiaso.net/shitposts/no-way-to-prevent-this/memory-safety/CVE-2026-123633/