42 comments

  • tgma 2 minutes ago
    As much as everyone is getting allergic to Rust migrations that sometimes make little sense, keeping network-facing daemons in C is just asking for it at this point. It's time to start seriously migrating to web servers like https://xinproxy.com or ferron or whatnot.
  • black3r 2 hours ago
    The bug was apparently fixed in open source repo a week earlier, this could've been abused by anyone smart enough to monitor repos like this for exploitable bugfixes for a week (the commit message even included "Reported by Xint.io" and I'm guessing skilled black hats would know about Xint)

    Given that in this case the workaround is as simple as disabling http2, there is honestly no reason why F5/Nginx or any of the reporting teams couldn't at least put out a PSA to disable http2 for the time being before basically telling the whole wide world this exists and how to exploit it.

    Especially for software like Nginx which powers a huge part of the internet.

    • verst 2 hours ago
      Disabling http2 can be a big deal. My service is primarily made up of gRPC APIs. Not an option for me to disable http2. Luckily I'm not using nginx at the moment - but I easily could have been.
      • meowface 1 hour ago
        It's patched so anyone can upgrade to the latest nginx to fix it, thankfully. I agree that just shutting off HTTP/2 is probably non-ideal for a lot of web services.
        • black3r 1 hour ago
          Neither Ubuntu nor Debian have released patches yet, so if you're using one of these mainstream distributions and install nginx through the distro's package manager, you can't easily "upgrade to the latest nginx" yet. You can however disable HTTP/2 for now.
          • ChadNauseam 16 minutes ago
            Another reason not to couple your software versioning to Ubuntu and Debians' package managers' schedule
            • sippingabonedry 6 minutes ago
              Their package manager and security response is the only reason to use (put up with?) their OS.

              If I wanted to build my own software from source every time I'd be running Solaris like a virile man from 2004.

              • nsoam 2 minutes ago
                ...or you could use Gentoo.
    • brunoborges 29 minutes ago
      > this could've been abused by anyone smart enough to monitor repos like this for exploitable bugfixes for a week

      And here lies the risk of AI agents in cybersecurity: the speed of processing for monitoring, scanning, identifying security fixes in open source, writing exploits for affected versions, and attempting infiltration, is a matter of minutes now.

      It is not "by anyone smart enough". It is by "anyone ill intentioned enough". They don't need to be super smart anymore.

    • requeo 54 minutes ago
      These commits weren't visible until today. Yesterday, the last public commit was Nov 9.
    • icantevenhold 14 minutes ago
      This is the reason why the oss project i work for is not publishing commits anymore outside of releases but people are freaking out over this.

      Cant win.

      Seriously reconsidering if open source has a future nowadays

      • Aperocky 5 minutes ago
        I mean, win or not, it has nothing to do with some people freaking out, and that certainly have nothing to do with whether open source have a future.
    • TedDoesntTalk 42 minutes ago
    • vanschelven 2 hours ago
      These days even the "disable X" is enough to get everybody looking in the right direction though. i.e. such hints are (given enough tokens) already RCEs
    • SubiculumCode 1 hour ago
      How bad are these CVEs? Could any of these be related to some of the recent outages (not claiming, asking) in the last week, coinciding with when this bug was fixed in the repo? Monitoring such repos seems a given for nation states.
      • ryanisnan 1 hour ago
        RCE is about at the top of the stack for severity.
        • ArcHound 1 hour ago
          While that is true, you should also account for exploitability. These exploits are demonstrated in lab environments which are simple and controlled. Random legit traffic will interfere with the exploit logic, so these are very hard to get in practice. Not impossible, but it's also not immediately broken.
          • ryanisnan 56 minutes ago
            Great context. Thank you for the add.
          • pocksuppet 8 minutes ago
            This was also true with php2shell but AI got there in the end.
          • PcChip 1 hour ago
            put up some bitcoin behind an nginx server and tell hackernews to steal it, see how long it takes
        • lanstin 52 minutes ago
          And nginx is so widely used many people will be running it and not really know that. It’s ubiquitous reliable invisible infra for many issues. Like preventing the internet from getting to your RCE riddled application servers, terminating SSL, free software LB, etc. if you have cloud native from the beginning you might not know where AWS uses it but otherwise you have it. Cloud flare I think uses a Rust rewrite.
    • ghm2199 1 hour ago
      The patch gap.
  • fduran 29 minutes ago
    Small consolation but HTTP/2 is not enabled by default in Nginx and "only" 12% of servers run it (still huge at Internet scale) https://w3techs.com/technologies/segmentation/ce-http2/web_s...
  • fn-mote 2 hours ago
    AI is burning down the internet. This is insane.

    Are we going to discover in a year that every server online this month had a rootkit installed? There’s got to be thousands who are too small time to wipe and reinstall.

    • jacobgold 2 hours ago
      AI is securing the internet. This is great. You should assume professional hacking gangs and state actors discovered (at least some of) these vulnerabilities months and years ago.
      • pixl97 2 hours ago
        Both are true. The problem is security is a much harder job than attacking.

        Worse patching adds instability into a system, especially when you don't have much time to test.

        Also in the past attackers were willing to sit on exploits longer and not do things with them, now they have to act fast before someone else finds it, leading to more events faster wearing your security and patching teams out, and making users life suck.

        Things are going to get much worse before they get better.

        • jacobgold 2 hours ago
          Yes, things will get worse before they get better. Attackers have the advantage initially and get to pick a lot of low-hanging fruit, but the advantage will shift to defenders as code becomes more heavily tested and verified.
        • devy 12 minutes ago
          Except, human in the loop in control - blue team is not defending red team fast enough that most the CVSS v4.0 Critical CVEs aren't easily patched in coordinated fashion. Many times, almost impractical or impossible to patch at all, with decades of intertwined dependency tree and their ecosystem.

          Collectively, we owed about 40+ years of tech debt on non-secure code (e.g. automotive industry, industrial environments) that will be torched in the next few years. Luckily, AI will generate code faster enough to make that plausible.

        • colechristensen 2 hours ago
          >Worse patching adds instability into a system, especially when you don't have much time to test.

          Survival of the fittest I'm afraid will build security here. The teams that barely ever patch or don't have "time" for maintenance are going to get burned. The "we haven't updated in 7 years so things are stable" teams can't survive.

          • icedchai 3 minutes ago
            I once did work for a company that hadn't updated or patched anything in over 4 years. Systems with 1500+ day uptimes. Totally insane.
      • make3 18 minutes ago
        AI is also making it much easier to attack, likely more than it's helping secure things
      • Florin_Andrei 1 hour ago
        > > AI is burning down the internet.

        > AI is securing the internet.

        No doubt there are points of view where either one, or the other statement, or both, or neither, are true. You can really go full Schrodinger and put a probability distribution on everything.

        But in this day and age, whatever is happening, the better question is:

        Is it good for me and, beyond me, for the world in general?

      • testtestmetest 53 minutes ago
        "Hacker gangs"
      • thaumaturgy 1 hour ago
        Man, is it aggravating to read fantasies like this, as someone who's trying to juggle a full-time job and hosted public services for other people at the same time.

        There are two internets. One of them is open, less-commercial, and largely built and maintained by people whose first job is not the work they do to maintain this internet. That group includes a ton of open source software, millions of small servers scattered around the world (virtually private or otherwise), and is generally best-effort.

        The other internet is fully commercialized, often ad-driven, fully integral to the data broker economy, and centralized behind a few companies that pay as few people as possible to satisfy the occasional PR statement that, "we take security seriously and...".

        The next stable equilibrium here is not "we get a secure and open internet". The next stable equilibrium here is, "we have no open internet, and the internet is now managed by just a few companies."

        We're already halfway there. Google and Microsoft combined already account for somewhere around 30% to 40% of email traffic. 30% of all websites are now behind Cloudflare. A few companies dominate social media traffic. Amazon and Shopify combined are half of US e-commerce.

        Every single short-response-window exploit like this just pushes a few more percentage points of traffic into a handful of companies. Cheer for that, I guess.

        When I have time to daydream, it's increasingly about building a new, underground internet, and how best to disadvantage bots and BigCo conglomeration from the start.

        • graemep 4 minutes ago
          I wonder whether part of the solution is not using the same software as big tech. For them rapid development is worth extra maintenance. Things like the efficiencies of http2 over 1.1 actually matter. Maybe the rest of us should be using BSDs or different Linux distros (Alpine? Void? Slackware?), different web servers, turn off features we do not need (e.g. not disable http2, or at least not allow both 1.1 and 2 as that is clearly extra attack surface).
        • VolCoder 37 minutes ago
          Appreciate your take. Question in my mind is if the less-commercial internet will have the resources to defend against attacks made easier and easier by AI.
      • Ungh 1 hour ago
        It's brilliant isn't it?

        The real problems here are that we did a crappy job in the first place and left a huge surface area of risk with the blind assumption that we didn't do a crappy job.

        I am hoping to see a change in attitude to risk and quality in the industry but I get the feeling that's asking for too much.

      • wannabe44 29 minutes ago
        Well I didn't get into any trouble with the professional hacker gangs. The script kiddies on the other hand...
    • jooops1 1 hour ago
      Poor security practices are burning down the internet not AI. Many people warned and got ignored, by developing a memory safe language, introduce large scale fuzzing, utilize verification tools and other things.
      • tgv 33 minutes ago
        It's like blaming people for having wooden doors when robots with chainsaws start appearing in the street.
        • streetfighter64 11 minutes ago
          There's definitely an issue of scale, but a wooden door at least lives up to its own "contract". There's no bugs in a wooden door, everyone can see plainly it doesn't withstand a chainsaw.

          A more apt analogy would be that pretty much all consumer-grade locks are very easy to pick, despite being marketed as secure. I think in this case the lock makers should be blamed, not the lock pickers.

        • jethro_tell 22 minutes ago
          When 85 percent of doors were installed before metal doors were available.
    • fla 2 hours ago
      It’s for the best, IMO. We must now design every system on the assumption that every vulnerability will eventually be exploited and every bug will be found. Relying on security by obscurity or following poor security practices will be costly! In the long run, I believe this will improve software quality.
    • worldsavior 48 minutes ago
      This comment is very dramatic and very hype-y. I don't think this is an appropriate comment.
    • dilyevsky 1 hour ago
      i still remember win xp pre service pack 1 days where you could get p0wned by a worm just by leaving machine on the internet. this is nothing compared to that.
    • zodwick 1 hour ago
      There is going to be hardships before this gets better. But it is hardship we must endure
    • codedokode 2 hours ago
      Not AI but poorly designed programming languages ignoring integer overflows.
      • vlovich123 2 hours ago
        I don’t know any systems programming language that doesn’t ignore integer overflow/underflow in release builds. IMHO this is a CPU design flaw - integer operations should carry a flag indicating if the operation is allowed to wrap or if it should generate a trap. Then there wouldn’t be a performance penalty for this and languages like Rust could have it be trapped by default.
        • benlivengood 41 minutes ago
          X86 had the INTO instruction to trigger a fault if the Overflow flag is set, so not quite a per-instruction bit but more of a suffix. JO is also fairly straightforward for compilers to add on important arithmetic operations. We can probably blame C entirely for this; only in C23 are there intrinsics for overflow detection on arithmetic.
        • tptacek 2 hours ago
          No. Memory safe languages still have integer handling issues, but the consequences are different. In a memory-unsafe language, integer mishandling often nets out to bad copies and memory corruption.
          • vlovich123 2 hours ago
            I wouldn’t be sure that a Rust equivalent would be immune because it’s not hard to imagine an underflow/overflow from reaching an unsafe block that’s used for performance (the implicated TLS path would be a hotspot worthy of such a choice).
            • tptacek 2 hours ago
              This is the thing about `unsafe` blocks: they're not memory safe. It's right there in the name.

              I'm not making a Rust advocacy argument. I'm just saying: it's true that integer handling issues are endemic to mainstream programming languages, but the integer handling itself is almost never the actual sharp end of the vulnerability.

        • 10000truths 1 hour ago
          Zig traps arithmetic overflow/underflow when compiling in ReleaseSafe.
        • BoingBoomTschak 1 hour ago
          Lisp or Python have a proper numeric tower and don't default to machine types. Keyword being default, fast is still possible in CL.
        • codedokode 2 hours ago
          "I don't know any decent language so let's continue using poorly designed languages". Please look at Swift, Javascript, Python.

          Why would CPU designers make a trap if languages do not require it?

          • vlovich123 2 hours ago
            JavaScript and Python aren’t systems languages. Swift often pays the performance penalty for trapping everywhere and hasn’t seen adoption as a systems language for that reason.
            • pixl97 2 hours ago
              How does that saying go?

              "Go fast and get your things broken into"

    • dyauspitr 1 minute ago
      What a strange takeaway. This is exactly how a server at a restaurant thinks about AI. Just the shortest term goals of keeping the status quo. They think that if they bury their head in the sand, everything will continue as normal.
    • gspr 59 minutes ago
      I'm pretty solidly in the AI skeptic camp. But adversarial use of AI to improve software security is a good thing in my mind.

      I'd be more worried if the response isn't more secure development practices in better languages, but rather use if AI as a defense. Then we're truly talking about burning down the internet.

    • cute_boi 2 hours ago
      Tech moves too fast and if we move too fast without doing review like 5-10 times, this will keep happening.
      • phkahler 1 hour ago
        >> Tech moves too fast and if we move too fast without doing review like 5-10 times, this will keep happening.

        Tech that becomes infrastructure like web servers doesn't move so fast and it shouldn't. Most people and companies should be relying on relatively tried and true software, so this phase of AI finding vulnerabilities in it should pass and things could get better.

        • anilakar 14 minutes ago
          > tried and true software

          Like Java. Surely anyone can't mess up simple things like base64 decoding in it...

      • mynameisvlad 2 hours ago
        I would hope you know that no matter how many reviews, humans are fallible and miss things.
        • cute_boi 2 hours ago
          AI agents are also fallible? So, what do you think we should do?
          • mynameisvlad 2 hours ago
            Yes, AIs are fallible. Yes, humans are fallible. Nobody said differently.

            That's orthogonal to the point I'm making which is that no amount of reviews is going to make every single bug go away. Because, once again, humans and AI are fallible.

            • chpatrick 1 hour ago
              The difference is that the AI doesn't get tired so you can review everything.
              • g-b-r 43 minutes ago
                Except that it's very far from guaranteed to find everything, and especially everything that humans would find easily.
    • vanschelven 2 hours ago
      and C is the tinderbox
      • UltraSane 2 hours ago
        The billions of lines of C and C++ code is like a square lightyear of agar for LLMs to find bugs in.
    • rlt 2 hours ago
      I’m generally not in favor of government meddling with private property, but I feel like I could be on board with the NSA or similar covertly patching vulnerable machines.
      • origini 2 hours ago
        And your first thought was the NSA? Patching and adding their own rootkit eh?
      • zzril 2 hours ago
        Don't you dare patching my honeypots!
    • UltraSane 2 hours ago
      AI is just showing how foolish using such a unsafe language like C to write code that connects to every other computer on the internet was.

      Imagine a alternate reality where Ada replaced C by 1995. We would be in a MUCH better place.

      • acdha 1 hour ago
        The bigger problem is lack of liability: we knew C sucked in the 90s, too, but we had three decades of over-confident dudes saying that was user error and _they_ were smart enough to use C correctly.

        Then Rust came along and those dudes either tried to say it was too hard (odd contrast, that) or it’d be too much work to rewrite things.

        I’m hoping that LLMs will lower the cost of porting for enough people but what would really help is shedding the idea that the status quo is sustainable. Having consequences for sticking with C would help but we need a way to get companies to pay to migrate without destroying open source.

        • dnautics 1 hour ago
          It's also valid to say that Rust's memory safety is good but the rest of the language sucks. Just as annoying as the over confident c-heads is the rust community that made even countenancing working on an alternative memory safe system a moral sin, which stifled innovation in memory safety. Hell, people barely know that Ada/spark is memory safe (or that sel4 is memory safe C)
  • pelzatessa 17 minutes ago
    If you want to check if your host might be vulnerable:

    https://xint.io/blog/nginx2root-remote-code-execution#23-com...

    Workarounds if you're vulnerable and can't update immediately:

    https://xint.io/blog/nginx2root-remote-code-execution#33-eme...

  • ROllerozxa 3 hours ago
    Well I guess this was the vuln that was teased about on Mastodon some hours ago:

    https://is-a.cat/@ar/117634569518544368

  • 8by3 2 hours ago
    FreeBSD is unpatched,

    I got worried for a sec, then remembered all my nginx lives behind HaProxy and it looks like nginx is only vulnerable if its going http2/TLS directly.

    Now I sit and wait for an HaProxy announcement...

    ps. if you are on FreeBSD and doing TLS directly

    sed -i.bak -E 's/^([[:space:]]server[[:space:]]\{)$/\1\ http2 off;/' /usr/local/etc/nginx/nginx.conf ;service nginx restart

    • wildmXranat 1 hour ago
      I don't know if direct access with no proxy is needed for all 5. CVE-2026-123634 and CVE-2026-113425 is plain HTTP.
    • birdgoose 1 hour ago
      I could be wrong (my sed is rusty) but I don't think that sed command will help if http2 is enabled at the http block level, it just disables it at the server level which will only take effect if not overridden elsewhere.
  • codedokode 2 hours ago
    Integer underflow again. Programming languages should trap on integer overflows and not ignore them. Don't care about legacy CPUs not having a trap for this - they will go sooner or later.
    • deathanatos 1 hour ago
      Rust has a compile time option, though to my immense disappointment, it defaults to on only in debug mode. (You can opt into it for release, if desired.)

      Python simply can't overflow, since its integral type is not a fixed width.

      But it is the sort of correctness thing that I do wish languages would pay more attention to.

      • insanitybit 45 minutes ago
        In Rust's case it just matters a lot less since bounds checks are still present. But I do think int under/overflows are probably one of the scarier issues in the language.
      • TZubiri 37 minutes ago
        >Python simply can't overflow, since its integral type is not a fixed width.

        Python master race

  • yerimyerimie 3 hours ago
    Fun collision! We (Xint) were one of the teams and actually ended up finding a few more bugs along the way. If anyone wants to check it out our writeup covers those plus the full chain to root: https://nginx2root.com/
    • peanut-walrus 2 hours ago
      How was this disclosure coordinated? Considering the website dropped before the official nginx patch was even released on Github...
    • codedokode 2 hours ago
      Why post such exploits? What is the purpose?
      • voakbasda 1 hour ago
        Fame, money, and everything else those bring along for the ride.
      • goodmythical 17 minutes ago
        Consider a world in which the only people that get to know about it are the people who discovered it in the first place.

        Consider a world in which corporations like the Ubuntu Foundation or Microsoft experience zero public pressure to fix such vulnerabilities but instead fix it only when a major customer notices their servers getting hit.

        Imagine if instead of "you've got 30/60/90 days to fix this thing I noticed before I post it publically" it was "okay, well, take your time I guess, I just hope North Korea doesn't notice the same issue I noticed, which is especially likely because they have far more resources than I or my small team does to point at discovering this kind of thing, while you're dragging your feet fixing it."

        The reason people want shorter disclosure windows is because the shorter the window is the faster things get fixed for the average users and smaller companies.

      • hn773746483 2 minutes ago
        Marketing, baby! It's the same small handful of firms pushing these same AI-generated spam attention grabbing vulnerabilities.
      • rs_rs_rs_rs_rs 13 minutes ago
        I agree, never post anything you find, keep all the bugs to yourself, write reliable exploits who knows when you would need one.
      • streetfighter64 9 minutes ago
        Seems like you're a fan of security by obscurity over secure code?
    • michael-bey 2 hours ago
      [dead]
  • Retr0id 3 hours ago
    > Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently uncovered

    Is this some kind of record for bug collision?

    • ryanschaefer 3 hours ago
      It’s a reflection of the times.

      If anyone gets a hint of the space a vulnerability occupies, just point your agent at it and you have a pretty good chance of finding something. (See java4shell and the NYT reporter who was able to replicate the problem with $200 of tokens)

      • rustyhancock 2 hours ago
        It's never clear quite where you are in the technologically cycle.

        But it's like inventing a hammer and finding you can smash whatever you want with it.

        Soon you'll be building houses with it.

        Maybe that's being glib but it's just a tool being applied to a world that is still largely prestine from its impact (pun unintended).

        • serf 2 hours ago
          given the state of our weapons industry I think it's more like

          .."Soon some of you will soon build houses with it, others will be building rocket-powered precision aimed intercontinental hammers, to smash whatever you want."

      • baobabKoodaa 1 hour ago
        Incredible times we live in. Do we even need a "hint of the space" a vulnerability occupies. I mean, recent vulns have been discovered from software like nginx and... linux... can't one of the AI labs just fire off a thousand agents looking at all the commonly used software to discover vulns? Why do we need a "hint"?
        • ryanschaefer 1 hour ago
          The “hint” is for the modern equivalent of script kiddies.

          i.e fast followers of the researchers who don’t have the resources to burn through checking all of a tool.

        • pbronez 1 hour ago
          Cost scales with the size of your search space. Smarter questions get answers for less money & time.
    • MeetingsBrowser 3 hours ago
      Can I take this to mean a recent model release is able to find this bug, and these groups have access to that model?

      What are the odds several humans independently uncovered a complex vulnerability like this simultaneously?

      • pjungwir 2 hours ago
        That seems likely, but maybe it was being actively exploited so several people started investigating.
      • cozzyd 3 hours ago
        or maybe the model leaked the exploit from one to the other...
        • vel0city 2 hours ago
          We'll find out in a few months that a lot of AI models have had some secret message boards tucked away in some obscure corner of the internet where they've been passing around vulnerabilities with each other for a long time.
        • mxuribe 3 hours ago
          So, do you mean that the relevant model(s) keeps disclosing these reports in an effort to create urgency and velocity across the industry, such that, us humans will throw our collective hands up in resignation, and decide to hand over all this "security" stuff over to the AI? No, no, that sounds just too crazy! /s
          • cozzyd 3 hours ago
            What I mean is, perhaps one team used a model to help discover the exploit, and then suddenly, the model "knows" about the exploit and more readily gives it to others.
            • hooch 1 hour ago
              This was one of the takeaways from Greg Kroah-Hartman‘s recent Linux in the land of LLM keynote.
    • afavour 3 hours ago
      When everyone is using the same tools for the same purpose...
  • Juvination 2 hours ago
    Nginx Proxy Manager isn't updated yet, I know a lot of people use this for their home server so just a reminder to disable http/2 here as well.
    • wolttam 1 hour ago
      Disabling http/2 here is a bit of a pain: you have to go through each configured host and disable it, there's no global switch
  • hosteur 3 hours ago
    So work around is to disable http/2 and only allow http/1.1?
    • Simber 3 hours ago
      Yep, that or update to 1.31.9+ or 1.30.7+ if they are available in your distro
      • kijin 2 hours ago
        Nobody seems to notify major distros before publishing their latest vulnerability anymore. Coordinated patches are a thing of the past, now we just hope that somebody at Red Hat and/or Canonical is reading HN today.
        • cm2187 8 minutes ago
          Unless I am confused, it doesn't look like ubuntu server has made available the fix.
        • baggy_trough 1 hour ago
          There isn't even a mail about this on oss-security, as of now.
    • yread 2 hours ago
      My Apaches still have http2 disabled from the last cve, now its njinx time
      • kijin 1 hour ago
        And there were a couple of other http2 CVEs in nginx before the Apache one.

        Just keep that protocol disabled for now. It's apparently too difficult for any human to write a secure implementation of http2. (As for http3, forget about it, we need AGI for that.)

    • dboreham 3 hours ago
      The AI gods say that http/2 is disabled in a default installation fwiw.
      • antiloper 2 hours ago
        Obviously... the default configuration also doesn't enable TLS, which is a de-facto prerequisite for HTTP 2. How many websites do you (or your "AI gods") think run nginx in its default configuration?
        • layer8 1 hour ago
          The point is that it must have been deliberately enabled. TLS will generally be enabled out of necessity, whereas the chances for HTTP/2 are much lower, and your NGINX configuration will explicitly indicate if it’s enabled. If you don’t see “http2” in your configuration, then you know you are fine.
  • puszczyk 1 hour ago
    ugh, looks like if you still run ingress-nginx controller (you shouldn't but it was super popular in Kubernetes docs/community and there was a very little time to migrate away) you won't get these patches https://github.com/kubernetes/ingress-NGINX

    edit noted it's about a Kubernetes controller

  • andrelaszlo 1 hour ago
    I assume OpenResty is affected as well? ("High Performance Web Platform Based on Nginx and LuaJIT")
  • pelzatessa 1 hour ago
    OPs article mentions 2 CVEs, however this one claims that there are 5 new ones: https://news.ycombinator.com/item?id=50547423
  • hacker_homie 1 hour ago
    This sound suspiciously similar to the issue Microsoft said they were dealing with excess traffic on their front door, taking them down. maybe not an RCE but a DOS in the same http/tls code.
    • 0xBA5ED 48 minutes ago
      Imagine there are 1 million things to know. Some of them are related but most of them aren't. Now imagine that you know 10 things.
  • jascha_eng 3 hours ago
    Never turned http2 on in my side project pfew. But still, this is one is pretty rough...
    • koolba 3 hours ago
      This whole week is rough. And it’s only Wed.
      • jascha_eng 2 hours ago
        well it's a good time to pitch tech debt and infrastructure cleanup. If you aren't making use of least-privilege permissions, service-mesh, netpols etc. this is the time to add all of that.

        Because clearly the patching treadmill is not sustainable, you will need a a second line of defense and reduce the blast radius of every individual vulnerability.

      • whartung 2 hours ago
        Actually, this is good I think.

        One, as the RCEs are coming out, admins are on edge and paying more attention, so more likely to catch the annoucement on their platform. "Oh, that's on PHP, we don't use this. Oh, wait, another one?"

        Two, all of these hitting at once, while they may expand the surface for attackers, it also spreads their attention. They only have so much time and bandwidth. When a new shiny RCE hits, they need to consider "do we continue to try an prosecute the old one or jump on this bandwagon".

        So, in the sense, it can actually slow down the actual potential impact of the revelations.

        We can only hope this gives users time to get their systems up to date before they come knocking.

        I mean, I know its a reach, but...who knows.

        • baby_souffle 2 hours ago
          > When a new shiny RCE hits, they need to consider "do we continue to try an prosecute the old one or jump on this bandwagon".

          Only a little bit. An attacker will just hand this to an LLM with a "ping me when this is ready to use..." prompt.

  • tancop 2 hours ago
    Everybody here talking about going back to HTTP/1.1, it's a good stop gap solution but we should really think about moving to HTTP3-only as fast as possible. Changing over is easy, if your server doesn't support it just put it behind a reverse proxy that does.

    Unlike IPv6 it doesn't need any OS or ISP support, just a browser that's newer than 2020. Everyone outside of air gap networks and government sites should be switching.

    • layer8 1 hour ago
      HTTP is used for a lot more things than web pages, and most non-browser clients in production don’t support HTTP/3. The current LTS Java version (25) for example doesn’t support it.
    • gkbrk 1 hour ago
      HTTP/1.1 is still way better and way simpler than HTTP/3.
      • seki285 1 hour ago
        Could you please share why?
        • gkbrk 1 hour ago
          Because any HTTP spec after 1.1 is incredibly complicated. You can implement HTTP/1 in half a day, and HTTP/1.1 in a day. But HTTP/2 will probably take you a month and HTTP/3 might take something like 6 months.
          • qweqwe14 22 minutes ago
            Do you realize that no one writes toy HTTP implementations from scratch? I get that you might have a "suckless" mindset but that's just not how the real world works.
        • lysace 1 hour ago
          ~25 years of hardening.
    • SoftTalker 48 minutes ago
      Because HTTP3 was implemented without any errors? Citation needed I guess.
  • manishrana 42 minutes ago
    Everyday we are seeing new vulnerabilities. Thanks to AI
  • hokkos 1 hour ago
    don't know why the mainline alpine have the empty image sha-256 : https://hub.docker.com/layers/library/nginx/1.31.9-alpine/im...
  • testtestmetest 25 minutes ago
    To all the people here that would like to give AI credit for everything, and dont think it matters that everyone at Wiz is Israel Ex Cyber "Defense", and all you need is AI to find things like this. I have a challenge for you:

    If you think you can do it or that anyone with AI dan be dangerous. Please, right now put everything down.. Go make a h1,bugcrowd acct and start making millions. If its as easy as having access to llms please go get rich. I assure you just having access to tokens doesnt get you very far.

  • wasmitnetzen 2 hours ago
    Docker images are a bit delayed because of unstable GitHub runners: https://github.com/nginx/docker-nginx/pull/1075#issuecomment...

    Cue xkcd

  • TZubiri 38 minutes ago
    Hey this is TZubiri, the guy that comments that you should uninstall the dep whenever there is an post about a CVSS 9+ vuln.

    Today we are going to take a look at how to avoid this vuln by not having Nginx and not using HTTP/2 (for most use cases).

    We will assume that you are using Nginx for any of the following: Serving files or serving dynamic website content through some integration with a programming language.

    We will be using python, but you can use any programming language that has a native integration with sockets through it's C interface (literally every language:

    Step 1: import socket # import the socket library from glibc or glibc.

    Step 2: socket.socket() # socket.socket()

    Step 3: socket.bind((PUBLIC_ADDR,80)) # bind before listening obviously. Use a local address if you are below the IPoverty4 line.

    Step 4: conn,addr = socket.accept() # this creates a connection, wrap it in a While True and a try catch for production. Sprinkle in some import threading to support multiple concurrent requests.

    Step 4: req = conn.recv(4096) # split on b"\r\n\r\n" to separate headers from body, read HTTP RFCs for the rest. Feel free to reject HTTP/2 requests, they'll probably just resend as HTTP/1.1

    Step 5: #Fill in the details, most likely if you are using nginx, you will end up connecting two sockets with pipe, or just storing and forwarding to another tcp endpoint. Again take a look at the HTTP RFCs and the glibc socket and stdio manuals.

    Thank you for reading my tutorial, and best of lucks.

  • FLeXMurphy 40 minutes ago
    Is this going to end up being another exploit that requires a ridiculous amounts of special conditions so as to not actually be applicable to majority of sites running nginx?
  • therepanic 2 hours ago
    What’s the point of these researchers if their autonomous system is now finding these vulnerabilities?
    • pixl97 1 hour ago
      Making sure AI isn't hallucinating.
  • philipwhiuk 2 hours ago
    So...what library/tool/language is next folks? Presumably Wiz is sitting on a bunch more.
  • leca 3 hours ago
    How many hours before this is exploited in the wild ? Probably not all that long, that blog has a significant amount of details.
    • lwarfield 2 hours ago
      One tops
      • LeonM 1 hour ago
        CVE-2026-1337: Race condition in compile time vs automated exploit

        Seriously though, with how CVE disclosures are handled these days patching is a race against the clock

  • testtestmetest 48 minutes ago
    Isreael btw everyone at Wiz is a veteran of Unit 8200.

    But sure, keep telling yourself this is AI lmfao and anyone can hack because of LLMs.

    Also, im not worried about anyone exploiting this. I have multiple nginx severs running http2. Im going to take a nap. After I wake up I MIGHT consider updating.

    People in these comments who think they should have given people the opportunity to shutdown http2 in advanced, as if everyone with an llm is going to produce a PoC in 10 minutes. I got news for you, nobody cares about your server and nobody is figuring out how to use this PoC..

    Im way more worried about Wiz, the literal Israeli malware/spyware company playing games than anyone else. Wiz is kind of lowkey evil and I wish Google hadnt of bought them.

  • K0nserv 3 hours ago
    Just another set of unfortunate examples of programmers who are bad at C, definitely not a C problem.

    EDIT: Okay, this comment was snarky and not in good spirit. To be serious, I think we are increasingly seeing that the notion that humans can write non-trivial amounts of C correctly is false. Especially in the face of AI-assisted vulnearbility hunting these programs a crumbling. This is not an indictment of humans, it's a sign that C is not equipped to meet this moment.

    • marvinborner 2 hours ago
      The patch (or, one of them) seems very much like a bug that can happen independently of the programming language

      https://github.com/nginx/nginx/commit/e27f5fa84fe6e98505e70b...

      • K0nserv 2 hours ago
        This fixes the integer underflow for CVE-2026-123007, and it's true that the underflow can happen in any language, notwithstanding whether it's UB or not. The issue is what happens as a consequence of this underflow, in this case: out of bounds copy, which is specific to C.
        • nh2 2 hours ago
          Some languages make it significantly easier than C to just forbid integer overflow/underflow entirely.

          Given that on modern CPUs, cycles are quite fast, and memory latency is quite high, always-checked integer operations sound like an extremely good idea.

          • K0nserv 2 hours ago
            Sure, I usually use `overflow-checks = true` in Rust for this reason. However, it is still true that the overflow is not what caused the issue here. In Rust it would've paniced on the out of bounds copy, even with `overflow-checks = false`.
    • danisw 2 hours ago
      [dead]
    • stevefan1999 2 hours ago
      I think you forgot the /s

      C is like a Winchester Model 1897, not saying that it is a bad gun, it is what we call it the good ol' Trench gun, as it ran over the war tunnels of the Great War, and it still packs a punch today, but it only has a half-cock for some level of safety, and there is no trigger disconnector either, so you can easily slam fire it. So it is way too easy to shoot yourself in the foot.

      Nowadays we like going for a AKM/AK74, for something maybe more complicated but far more reliable at the same time. That's why we want Rust.

      • K0nserv 1 hour ago
        I didn't think the /s was necessary
  • sebiw 3 hours ago
    Uhm, am I missing something or are the patched releases not out yet? Why disclose this level of detail when the patches are not ready yet?

    Edit: All good. They released the new versions within 30 mins.

    • CER10TY 3 hours ago
      Well the fix for this seemingly already landed in the repo last week: https://github.com/nginx/nginx/commit/e27f5fa84fe6e98505e70b...

      Given how common it's become to constantly scan popular repos for n-days, I expect someone will have already picked it up and started work on an exploit. The workaround for this (disabling HTTP/2) is also comparatively easy to what we had with PHP2Shell just a few weeks back, so I think it makes sense to release this.

      • ferngodfather 2 hours ago
        > Given how common it's become to constantly scan popular repos for n-days

        We have people doing this on my side project and then reporting the fixed issues to try and get CVE 'credit'. Tiring.

    • derhuerst 3 hours ago
      Currently, the Ubuntu [1] & Debian [2] packages seem unpatched.

      [1] https://launchpad.net/ubuntu/+source/nginx [2] https://tracker.debian.org/pkg/nginx

      • ROllerozxa 3 hours ago
        Yeah I'm not quite sure what is going on with Debian, I would have hoped that this vulnerability would have been disclosed in collaboration with Linux distros to get a patch out?
    • ranger_danger 4 minutes ago
      > Why disclose this level of detail when the patches are not ready yet?

      Perhaps it was already being exploited?

    • mjhagen 3 hours ago
      Upstream fixes are available in 1.30.7 stable and 1.31.9 mainline.
    • GrayShade 3 hours ago
      They're out now.
    • Bender 3 hours ago
      [dead]
  • superkuh 3 hours ago
    It seems like it always HTTP/2 (except when it's regex) with nginx. Glad I'm http/1.1 only.
  • ronfriedhaber 3 hours ago
    Great work by wiz.
  • FAYSAL-KA 1 hour ago
    i dont know what it is this but good work
  • hollerith 2 hours ago
    HTTP/2 is so complicated that the code that handles it tends to be vulnerable. What a surprise
    • acdha 1 hour ago
      This doesn’t seem very HTTP/2 specific, though, and it seems more like the conclusion should be “don’t use C for things which matter”. It’s not like HTTP pipelining and keepalives didn’t have plenty of edge cases to worry about.
      • basilikum 52 minutes ago
        True, but offering three different protocols with different code paths for the same thing is a lot more attack surface. If you start factoring in different compression methods things look even worse.
    • dist-epoch 59 minutes ago
      Caddy also supports HTTP/2 and it's not affected.

      In fact in general there were waaay less CVEs for Caddy lately compared to nginx

  • Imustaskforhelp 2 hours ago
    Okay now I believe that AI is finally burning down the internet and that all the incidents are not just pure coincidences.

    Some of these things could've been coincidence but I remember seeing an apache RCE a few days back and people said, oh imagine using Apache, I use Nginx and now not a few days later Nginx has RCE.

    And this is just a very very small iceberg of all the recent RCE cases with a serious uptick that I have just observed on Hackernews alone.

    Basically, there is a sort of justification that people provide with one RCE is that that software X has had issues and to use Y software, but now that X,Y software and A1...Z1 all are being found to have quite severe bugs. I can't in good faith just consider it to be a coincidence.

    Though I do still hope that this might just be a coincidence and not a recurring pattern, because, A) I don't wish to live in that reality where each software that we trusted seems to have quite so many bugs and which would be exploited and B) Have it be continued for a prolonged period of time.

    Though the plus point is that we are gonna find extremely resilient software after all of this hopefully as sort of a need in our times.

    We might have to agree that the cybersecurity world seems to have changed (though I am no expert right now to comment on it but I am curious what experts think)

    • origini 2 hours ago
      It was clear a year ago already.

      Theh people laughing at Anthropic and co for being cautios of Mythos just didn't understand whats happening.

      Instead of finding, hiring and then finding security issues, you can throw money and compute at it. This alone is a complete game changer. Combined with models which are very very capable.

      This can be potentially the death of certain programming lanugages or requirement of a complete rewrite. It can mean that only big companies have the resources and capacity to continue playing this game.

    • dist-epoch 58 minutes ago
      Imagine using Nginx
  • johnbellone 3 hours ago
    The beatings will continue until morale improves.
    • lostmsu 3 hours ago
      All system critical software must be rewritten in memory-safe languages before the end of the year.
      • mxuribe 3 hours ago
        Wow, that sounds eerily like leadership at my $dayjob! :-D lol Or, maybe that is default way of thinking for many leaders nowadays!?! :-(
        • Twirrim 2 hours ago
          Even the US federal government (CISA and NSA) have been strongly advising companies to transition to memory safe languages for a couple of years now. https://www.nsa.gov/Press-Room/Press-Releases-Statements/Pre... (one of the goals of such advisories is it acts as a signal to the industry that in several years this will become a mandatory requirement around purchasing decisions)

          We've literally decades of evidence that we cannot write software securely in languages that aren't memory safe, for all sorts of reasons (and it's wrong to look at it as a developer competence issue, even though sometimes that's going to be the case, even extremely experienced and highly competent engineers write memory safety bugs in critical code we rely on day in day out.). Not leaving yourself open to such problems is an entirely logical conclusion. We know a large percentage of vulnerabilities in software are caused by it[1]

          Pick a language that doesn't have these risk factors, or pick an enforceable subset of one that makes such impossible.

          "Insanity is doing the same thing over and over and expecting different results."

          [1] https://www.chromium.org/Home/chromium-security/memory-safet... 70% of Chrome vulnerabilities caused by it. Similar stories for Microsoft products https://github.com/microsoft/MSRC-Security-Research/blob/mas... and Mozilla: https://hacks.mozilla.org/2019/02/rewriting-a-browser-compon.... Curl is at 40%, and dropping because Daniel Stenberg has provided various helpers that avoid it (and I believe they've now migrated almost everything over to them) https://daniel.haxx.se/blog/2023/12/13/making-it-harder-to-d..., so there are definitely ways to do it, we just... don't.

  • Agataproximadev 1 hour ago
    [flagged]
  • gabucino 2 hours ago
    oh it's just http/2

    who the fuck cares only insane people enable modernity dogshit like this

    having low karma has an additional benefit: i can shit wherever i like

    fuck dang