r/programming • • 4d ago

Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007

https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
942 Upvotes

118 comments sorted by

1.0k

u/TINTINN95 4d ago • Bravo

I'm tired boss

43

u/dhensche 3d ago

We have a huge portfolio of Java apps impacted by Java 4 shell yesterday as well. This comment has been on repeat in my head all day

6

u/Caedendi 3d ago

Dog-tired

1

u/PresentationOk9370 2d ago

this shit is getting out of hand.

115

u/fooby420 4d ago

NGINX4SHELL?!?!

74

u/sorahn 4d ago

27

u/DragonSlayerC 4d ago

Instead of nginx4shell we have nginx2root. The root of 4 is 2. Coincidence? I think not!

7

u/aes110 3d ago

At this point people should start buying up all these domains and sell them when the inevitable exploit arrives

44

u/obetu5432 4d ago

2shell4me

10

u/git_push_origin_prod 4d ago

2shell 2furiuos five, RCE drift

-5

u/unknowinm 4d ago

2girls2cup

384

u/Doctor_Beard 4d ago

I want to get off Mr. Bones Wild Ride.

76

u/starliight- 4d ago

The Ride Never Ends

68

u/sigma914 4d ago

It will in a while, AI accelerated workflows have 40 years of deployed crap to work through. There's plenty of low hanging fruit. The bugs found/value produced will tail off as the easily identified/high impact bugs get found and fixed.

68

u/hbarSquared 4d ago

Haven't you heard? It's the age of the 10x engineer, we're pushing slop to prod at rates unimaginable just a decade ago.

32

u/sigma914 4d ago

Sure, but the high impact bugs are always in stuff like the kernels, language runtimes, web servers, crypto libs etc. Those are going to be hammered by security tooling as changes are released.

Doesn't really matter if slop app 500,007 with revenue < the cost of the tokens it takes to run it's build script produces a new vulnerability per day since barely anyone's using it anyway.

The big finite gold deposit of impactful bugs in stuff that's actually deployed and used is being strip mined at way beyond replacement rate. The valuable bits will be cleaned out in a while

9

u/Narthorn 4d ago

True for projects that don't use AI, but anything that's currently being sloppified is actually in a way worse situation than before.

It's still the same old attack/defense asymmetry, defenders have to make everywhere robust, while attackers only have to find a single place with a critical vulnerablity.

Whenever you add code, you have potential new vulnerabilties not only in what you just added, but also in every interaction of the old systems with that new code, so the attack surface scales exponentially, not linearly, with the amount of code added.

So when you 10x the amount of code...

5

u/sigma914 4d ago edited 4d ago

I'm not disagreeing that AI os going to generate huge amounts of risk and unseen before numbers of vulnerabilities. I'm just saying the core infrastrucutre pieces are going to be hammered with a huge amount of defensive work and their bug count (at least critical ones that already exist) will be mined out.

Those core bits of infrastructure have better engineering practices and actual expert eyes on them, so I think the admission rate of crap slop will be lower than the bugs fixed.

The real threat is to individual projects and companies who will individually suffer under their own mass of slop bugs rather than us seeing an ever increasing amount of global outages/bugs

1

u/Popular_Exit_3624 3d ago

Man I work closely with infra team and for last couple of months we have been working on fixing the core vulnerabilities. We fix one and next day a new vulnerability comes. It’s so frustrating.

1

u/red75prime 2d ago edited 2d ago

So when you 10x the amount of code...

You have more vulnerabilities than the lines of code. I'm very skeptical about this exponential growth. Quadratic, maybe, if agents are instructed to never examine code that interacts with the changed or added code. Nah, there's no reason to believe that the situation will be any different from the humans-making-errors situation. Agents have larger "working memory". They can take into account more pre- and postconditions.

1

u/Narthorn 2d ago

I'm not saying that the situation will be very different from the humans-making-errors (we were already ourselves adding way too much code, even before AI), I'm just saying everything is going to play out much faster than before.

You have more vulnerabilities than the lines of code.

You have more regular bugs than security vulnerabilities, so at some point the code stops working at all (and then you hope that the thing that just broke wasn't the cloud infrastructure required to run the AI, because no human is going to be able to dive in the code and fix it anymore).

5

u/efvie 3d ago

You have no idea how many bugs are being introduced by slop every second of every day, man. On top of the unreal degree of decoherence and lost ability to reason about your systems, nobody is going to have any idea what's happening anywhere in <5 years if this insanity doesn't stop.

5

u/boofaceleemz 4d ago

There’s a finite number of vulns in old code. It’s gonna be a wild ride but it’ll slow down eventually as that becomes mined out.

The question is whether the new AI slop will replace it at the same pace. I’m kinda optimistic it won’t (not that it won’t be a lot of insecure garbage getting pushed to prod every day, but it’s not the same as the entire history of legacy code we have now being pored over).

3

u/ReginaldDouchely 3d ago

Until the fixes cause new vulns :(

255

u/SpareIntroduction721 4d ago

How about we just block all ports. Fuck it, internal use only. We create our own sandbox that has access to boring ass archive.org and that’s it.

70

u/Fahrain 4d ago

Recently, there was a bug right in the kernel - right before any interaction with the firewall and ports.

35

u/SpareIntroduction721 4d ago

What’s it going to do if there is no access to the web? Lock it all down. Everyone gets their own sandbox with notepad.

20

u/OffbeatDrizzle 3d ago

electromagnetic side channel attack from 500m away

6

u/mcgrewgs888 3d ago

Doesn't notepad have forced Cortana integration now?

14

u/TomerJ 4d ago

Cut the hardline at the mainframe

4

u/postmodest 3d ago

Like some kind of Black Wall?

3

u/AminoOxi 3d ago

Pull the plug

2

u/xThomas 4d ago

Nah, better idea

Attack the rest of the internet snd take it down first. Then it can’t take you down.

3

u/Hottage 3d ago

You're going to trust your local network clients?

A bold move. Probably safer to just not connect the network cable.

3

u/SpareIntroduction721 3d ago

Local? Network? Sir, you have access to notepad. Please send your inquiries via certified mail.

2

u/Hottage 3d ago

Imagine the damage someone could do spamming the A key into notepad.exe.

1

u/card-board-board 3d ago

Looks like CD-ROMS back on our menu, boys

47

u/lerrigatto 4d ago

I was so pumped by the java one and the ssh one and the kernel one, I couldn't wait for an nginx one

21

u/philipwhiuk 3d ago

There’s another PHP one dw

3

u/cbigsby 3d ago

Don't forget the Ruby ones

3

u/matthieuC 3d ago

The CVE says it's only vulnerable of you use a non standard configurations.

9

u/LaM3a 4d ago

They will all return in Doomsday.

138

u/Jaded-Asparagus-2260 4d ago

Well at least just like the Apache HTTP2 issue a few days ago, this one can be mitigated as well by just disabling HTTP2.

236

u/Abject-Kitchen3198 4d ago

This is not published yet, but almost all vulnerabilities can be mitigated by disabling HTTP/1.X as well.

120

u/Captain1771 4d ago

They don't want you to know this, but you can just shut down your VPS to prevent it from getting exploited by vulnerabilities

8

u/RiotBoppenheimer 4d ago

Computers were a mistake.

4

u/AminoOxi 3d ago

Let's just reinstate fax machines

5

u/Bhraal 3d ago

Computers are fine. It's the internet that's the mistake.

1

u/mycall 3d ago

Time to collapse all the layers of abstraction and make one blob that does it all. I'm working on it...

2

u/jlp_utah 4d ago

Hackers hate this one little trick....

-2

u/screwcork313 4d ago

I'm pretty glad I decided to give up running a VPS some years ago.

22

u/tom-dixon 4d ago

Disable HTTP3 too: https://app.opencve.io/cve/CVE-2026-121810

And TLSv1.3 too: https://app.opencve.io/cve/CVE-2026-118899

At least RCE can be avoided for all of these by having ASLR enabled, attackers will just crash the server.

10

u/baronas15 4d ago

If that doesn't fix it, just disable all tcp traffic, hell, even udp

1

u/AuroraFireflash 3d ago

this one can be mitigated as well by just disabling HTTP2.

Not completely, but it does help.

71

u/tankmode 4d ago

surely the AI can just roll out the fix by itself right?   thats why we dont need engineers anymore ?

19

u/git_push_origin_prod 4d ago

apt-get update --fuck you --payme

34

u/Dunge 4d ago

Oh damn, that will teach me to sit on a deprecated project (kubernetes ingress-nginx) that I can't just upgrade to the latest easily.

15

u/Forward-Outside-9911 4d ago

Traefik ;)

8

u/Dunge 4d ago

Yeah Traefik looks good but my problem is more of the k8s ingress > gateway api change than the reverse proxy software itself.

4

u/Forward-Outside-9911 4d ago

Ah yeah I also need to move to gateway api at some point. But traefik ingress is supported and from what I recall has exact compatibility with the nginx ingress stuff so you can migrate without much effort.

3

u/Dunge 4d ago

I'm using so many custom configurations that no matter what switch I do will require a bit of effort. Using gRPC server streaming which required to bump up a few timeouts, using udp/tcp routing, ip preservation via the proxy protocol, regex url rewrite and base path changes, eks load balancer targets, etc.

Yeah that's my day booked for sure.

1

u/unknowinm 4d ago

1 day? It’s a week. I use envoy gateway api which has the better support than all the other options.
Istio is also based on envoy but for some reason it doesn’t have the same support.
You also need to upgrade CRDS of gateway api and watch out that the UDPRoute moved from alpha to stable (if I remember correctly)

You can also try kong or the other one with agentic something which also have good coverage for the features.

3

u/Zaliron 3d ago

We tried looking for alternatives a few months ago that would allow us to keep using Nginx, and one company offered to maintain a patch for 10k per cluster.

1

u/Dunge 3d ago

nginx gateway fabric is the one to keep using nginx and the gateway api. I just finished my migration successfully. Where's my 10k$?

2

u/roastedferret 4d ago

I just had to deal with this in two K8s clusters. What I ended up doing was migrating to the Gateway API via Envoy. I was stupid and didn't reserve IP addresses, so I had to do a DNS change (easy with terraform, thank God), but it was a fairly involved migration.

1

u/wzrdtales 9h ago

With ingress-nginx retired, we needed a successor for our own clusters that would not mean rewriting and re-testing hundreds of Ingresses. So we built wxingress, a fork of NGINX Ingress Controller that reads ingress-nginx's annotations, ConfigMap keys and IngressClass, and uses its defaults. It also exports the same Prometheus metrics, so existing dashboards keep working.

- Parity test: 97 Ingresses (anonymised production + GitLab/Argo CD/Keycloak/oauth2-proxy charts + one per annotation), 2562 probes, 2511 identical answers. The 51 differences are documented.

- No Lua; endpoints update without a reload through an NGINX module. In our benchmark, about 4x the HTTP req/s of ingress-nginx 1.15 and half the CPU per HTTPS request (script in the repo).

- Hardened image (no shell, no package manager, read-only root fs by default), signed releases with SBOMs.

- A runbook for RKE2's bundled rke2-ingress-nginx, switching node by node. We switched our own production clusters this way (1 to 21 nodes).

- Gateway API is included, so you can move routes later, one at a time. It takes its logic from NGINX Gateway Fabric and passes the conformance suite, but we haven't battle-tested it in our own production yet, so feedback there is very welcome.

- Lua snippets need porting to njs; there is a guide.

- EUPL-1.2, maintained by us long-term since we depend on it ourselves.

Repo: https://github.com/wx-one/wxingress

Migration guide: https://wx-one.github.io/wxingress/migration/ingress-nginx/

If an Ingress behaves differently for you than under ingress-nginx, that's the bug class we care most about. Happy to answer questions.

83

u/TheESportsGuy 4d ago

Remember when the top comment in r/programming was almost always a detailed discussion of the issue in the OP? Pepperidge Farm remembers.

9

u/Flagyl400 3d ago

I remember when r/programming was a default sub.

12

u/rawbdor 3d ago

I remember when people in r/programming actually programmed by hand ;)

30

u/rookie-mistake 4d ago

this complaint also being formatted into a dated meme reference is honestly performance art haha

not wrong though

9

u/TheESportsGuy 4d ago

Pepperidge Farm also remembers when Pepperidge Farm cookies didn't taste like shit stuck to cement.

58

u/witness_smile 4d ago

Oh good thing no one uses HTTP/2

13

u/emdeka87 4d ago

gRPC entered the chat

19

u/unknowinm 4d ago

We use http67

1

u/shawntco 3d ago

That's the protocol I use to send sound clips of the FAHHH meme

5

u/pohuing 3d ago

They posted on reddit, using http/2

1

u/civildisobedient 3d ago

Stateful TCP for the win!

11

u/bwainfweeze 3d ago

Oh ffs.

Yesterday: Hey I’m safe from the JVM bug because everything is behind Nginx.

Today: fuck me, right?

14

u/kian_no 4d ago

It's becoming like tax office. They know exactly what they get but still we need to file it every time

7

u/MagnesiumOvercast 3d ago

NGINXcels seething at Caddychads.

15

u/DragonSlayerC 4d ago

Both memory handling errors. Time to RIIR (Rewrite It In Rust).

14

u/jakewins 4d ago

Honestly at this point running anything *frontline* internet that's written in C/C++ is *bananas* to me, like why would you possibly take the risk? Even the absolute creme-de-la-creme best-of-the-best most-battle-tested C/C++ codebases are blowing new holes in my stacks every week.

Java honestly similar, for different reasons - the final straw for me there was log4shell; the culture of making everything runtime configurable mutable transmogrifying little cleverness things, plus *massive* surfaces of *ancient* libraries.. I spent a decade in low level Java, not putting that on a network interface, no thank you.

1

u/bwainfweeze 3d ago edited 3d ago

Java hit literally everybody’s second system syndrome for architecture and its rotten with over engineering. Enterprise Fizzbuzz is a lampoon of Java best practices.

I really like Java the programming language, but the library is awful and your peers are the fucking worst. And they treat Josh Bloch like he’s a saint when he is the devil. He wrote the Java collections API without understanding type theory, and confessed to it after the fact. Take your UnsupportedMethod and shove it right up your ass, Josh.

44

u/Keeyzar 4d ago

Where are all the people who said ai finding vulnerabilities is a marketing gag?

How you feelin? 

75

u/Stetsed 4d ago

The problem was a lot of people myself included knew that if COUOD be dangerous, the problem was a lot of the same companies overstated what they actually got, or for example in a case with Firefox had disabled a bunch of security measures which yeah made a lot of people go “what”.

And it’s exactly the problem, it becomes hard to tell the difference between marketing and what the actual danger is.

-9

u/xMoody 3d ago

Lotta words to say you got baited and outsmarted

-10

u/Axxhelairon 4d ago

a lot of companies overstated what they got because most companies aren't tech companies and have no technical understanding, you should absolutely already be aware of this and have that insight over other people outside of the field and it's unfortunate for the rest of us that you don't and/or choose to perpetuate ignorance

it isn't hard to tell the difference between marketing and danger in many cases, and exactly like this one when you're looking at a vulnerability report for a remote code exploit. it's actually honestly unbelievable how much effort has to be spent on "convincing" people like you simple knowable facts like the sky is blue and that AI has an impact

26

u/hidegitsu 4d ago

It was both. The tools expose issues in a real and impactful way that has real world effect. The companies then used that fact as a marketing stunt.

38

u/dashingThroughSnow12 4d ago

Strawmen you create often blow away when you ask where they are.

-3

u/OffbeatDrizzle 3d ago

no... u?

2

u/NegativeSemicolon 3d ago

Vulnerable probably

1

u/Fuzzy_Paul 5h ago

Nobody stated that, all other statements about cloud are a marketing gig.

-12

u/bureX 4d ago

We did have automated vulnerability scanners and code analyzers for a very long time. Automated vulnerability discovery was already a thing.

I have no idea who are you shaking your fist at.

4

u/Necessary-Town-126 4d ago

Yes with fixed rulesets with ancient old vulnerabilities in it. And no intelligence at all to combine / exploit or think out of the box. Traditional scanners are nothing compares to what ai agents offer.

1

u/bureX 4d ago

I’m aware. I’m asking the guy who was the person who said AI vulnerability scanning was a marketing gag and who is he shaking his fist at.

4

u/hypnoticlife 4d ago

They are totally different things. You’re talking about scanning for _known_ vulnerabilities via published reports or static analysis. Right now AI is discovering _unknown_ vulnerabilities also beyond what static analysis has provided.

0

u/bureX 3d ago

Uhhh, code scanning tools have been finding vulnerabilities which are not “known” (beyond just running Nessus for CVEs).

AI assists in all of this a lot and expands in what the possibilities are, but let’s not pretend that people haven’t seen this before.

-5

u/Keeyzar 4d ago

Thank you. I can't believe they still try dyin' on that same horse, but gettin ridiculous with that. :D

2

u/morphemass 3d ago

Patch time? Again?

2

u/bwainfweeze 3d ago

I used to say, “time to make the donuts” but nobody recognizes that anymore, except Ryan Reynolds who altered it to “time to make the chimichangas.”

2

u/ThePickleConnoisseur 3d ago

This is why I still use punchcards as god intended

5

u/Entmaan 4d ago

Would you look at that, a memory issue... Wonder what we could do about that /s

2

u/bwainfweeze 3d ago

The big danger that nginx.com faces is that the more features they paywall the easier it is for someone to create a replacement. There are only about two features of the paid version that make me consider other alternatives and those alternatives mostly have them for free.

If you’re Nginx you want devs using the free version so that familiarity leads them to the paid version. I don’t think they’re doing that wel right now.

7

u/tophatstuff 3d ago

Hot take, but the only people who should enable HTTP/2+ on public-facing endpoints are CDN operators. Everyone else, turn it off.

This is an engineering decision that has let me skip several would-be emergencies and keeps paying off.

7

u/agentoutlier 3d ago

Many disagree:  https://http1mustdie.com/

Now with AI desync attacks could be more possible.

5

u/elmuerte 3d ago

And all the HTTP2 and HTTP3 implementations have plenty of bugs in the payload processing allowing, amongst others: request smuggling.

So yeah, HTTP1 implementations often screw up dividing header and body. But the new protocol implementations are not much safer yet. In fact, due to the complexity of multiplexing, I wouldn't be surprised that more attack vectors will show up.

3

u/agentoutlier 3d ago

Despite my comment appearing that I’m against 1.1 I am not. Just playing devils advocate.

HTTP/2 end to end is quite difficult to get right and often requires mTLS in some settings which is its own headache.

-2

u/bwainfweeze 3d ago

Agreed, with notes. The cost benefit of HTTP/2 and 3 is largely proportional to the speed of light delay between the source and the sink. Using the grug brained implementation behind the ingress is worth entertaining at least.

Where that gets a little weird again is fanout. Or more precisely, recursion depth because the cost of fanout is approximate to the slowest response rather than the sum. Depth is sequential.

4

u/Hottage 3d ago

I read this like it was Geordi LaForge giving a techno babble explanation of why the Enterprise is stuck in a time loop.

1

u/stgiga 3d ago

It seems like 2026 is the year of security holes

-3

u/gandalfmarston 4d ago

Welcome to the age of AI.

-22

u/SquiggerDigger 4d ago

Lots of sketchy darknet places rely on nginx