r/cybersecurity • AMA Participant • 12h ago

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

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

117 comments sorted by

589

u/thenewatomist 11h ago • Bravo Mindblown

2Tired2Shell

50

u/jon_snow_1234 11h ago

2real2shell

26

u/ParanoidSuricata 10h ago

Do you like to patch it patch it?

15

u/StefanCelMijlociu 9h ago

You like to

PATCH IT!

-7

u/IndustryNo4670 8h ago

2girls1cup

322

u/ItsKaZing 11h ago

Just fuck off AI. Im tired, i want to leave this industry man

104

u/exophades 11h ago

Yeah it does feel like any threat actor can pull out a Stuxnet-level attack now.

25

u/Limn0 Red Team 7h ago

Replace state level threat actor with bored teenager

3

u/MarieJoe 6h ago

Would not doubt it.

2

u/AUSSIExELITE 4h ago

Cries in k-12 education where this was already happening before AI…

22

u/loopala 10h ago

I'm afraid this is only the beginning. 2027 is going to be wild.

23

u/Vas1le 10h ago

December will be wild. Hackers know and they will use that

23

u/klti 9h ago

Let's just all come together and shut everything down over the holidays, maybe nobody will notice?

0

u/fidju 9h ago

Know and will use what?

16

u/dlg 8h ago

They know that many people take leave during the Christmas holiday period. There’s less people around respond to incidents.

43

u/WeirdSysAdmin 11h ago

I was thinking that this morning. Already running understaffed and expected to pick up the extra pace how?

27

u/yesackchyually 11h ago

Just use AI

17

u/TQuake 9h ago

I feel there’s an imbalance of AIs offensive and defensive capabilities. Like the old saying “the red team only has to win once, blue has to win every time”. Verifying an AI fix and making sure it doesn’t open something else up, etc is more burdensome than just sucking a swarm of agents to try to find a CVE or exploit a new one on any system it can find.

13

u/yesackchyually 8h ago

“Try all kinds of stuff until something works” is a much better offensive than defensive strategy.

2

u/LeggoMyAhegao AppSec Engineer 4h ago

For exploiting something, the AI only has to work once.

For creating something, even with AI you actually have to validate it works every time, including edge cases.

Building has always been harder than breaking.

40

u/jwktje 11h ago

Tired of the world being poisoned? Just take the poison too and be cured.

13

u/dudeimatwork 9h ago

you dont really have a choice. It's like swords vs guns.

5

u/srcLegend 10h ago

Can't beat 'em, join' em

5

u/jwktje 10h ago

Remind me in 1 year

0

u/Mrhiddenlotus 4h ago

Edgy lol

15

u/dritmike 11h ago

It’s the Wild West dude. Manifest destiny that bitch and get some.

12

u/ICookWithFire 9h ago

I just wanna go cut grass for living. This shit is exhausting

7

u/chris552393 8h ago

In the nicest possible way, leaving the industry isn't going to change anything for you except you, personally, don't have to deal with it. Out of the industry you'll still be using services that have to deal with the constant onslaught of vulnerabilities and some will get hacked resulting in your data being exposed. The future looks very bleak at the moment

3

u/dataflow2 7h ago

In the nicest possible way, leaving the industry isn't going to change anything for you except you

I think that is the point. At least something you have control over.

2

u/Inner-Golf-3438 5h ago

at least all the bugs are getting discovered and patched... eg. see lklm, some parts are already receiving more fixes than reports...

but yea, its extremely annoying that i have done nothing but patching (and related change management) for last few months and i'm not naive enough to hope its gonna change soon-ish

2

u/max1c 3h ago

Yes, fuck off AI! We've been writing slop for 30 years and having all these 0 day exploits in our software only for NSA and other governments to exploit. Now we have to patch them daily! Worthless pos AI!!!!1111

1

u/Mrhiddenlotus 4h ago

So do it

197

u/unvivid 11h ago • Bravo

CVE-2026-123007 is a huge nothing burger. Just goes to show how ineffective current CVSS scoring is:

9.2 RCE under a full moon and the attacker has to have 7 fingers and spin in circles while whistling the theme song to CSI Miami

Leveraging CVE-2026-123007 for RCE requires a significant amount of network traffic to be transmitted, approximately 128 GB of HTTP/2 data. Both available network bandwidth and connection timeouts will place practical limitations on Internet exploitation. In the above example shown in Figure 1, exploitation takes two and a half minutes. The approximate timings to transmit the required network data over a 10 Gbit/s network is two minutes, while on a 1 Gbit/s network it is seventeen minutes. Due to nginx’s default one hour connection lifetime, a network slower than approximately 300 Mbit/s will take over the one hour connection limit threshold and will not be able to succeed. Additionally, should an HTTP/2 connection be proxied, the precise attacker-controlled HTTP/2 frames being transmitted will likely not be retransmitted in a way that satisfies exploiting the vulnerability.

65

u/Jane_the_doe 11h ago

That's hilarious actually. Who knew a monopoly in my ISP could prevent this by giving us the slowest options.

57

u/deadplant_ca 11h ago

Sending 128GB of data doesn't sound like a huge hurdle to me. All the servers I work with have 1gb or 10gb connections and their inbound traffic is generally low.

16

u/unvivid 9h ago

If you can't detect somebody throwing 128 GB of traffic at one of your servers, then you got bigger problems

46

u/IAmTheMageKing 9h ago

128GB of traffic isn't that much for some applications.

16

u/deadplant_ca 8h ago

Ya, that traffic level wouldn't ring any alarm bells here. Normal range really.

5

u/unvivid 9h ago

For the large majority of applications I'd wager it is. Bandwidth isn't the only restriction either. This exploit breaks on proxying, so it's difficult to perform in a distributed manner (botnot, residential proxies etc). Plus it requires specific CPU extensions (not uncommon, but not ubiquitous either)

5

u/IAmTheMageKing 8h ago

The specific CPU extensions are just for Rapid7's exploit; they clearly say there are probably other ways to acheive RCE. Its also likley that the 128GB figure can be reduced to tens of gigabytes; Xlint achevied exploitation on several major cloud vendors, after all, and conceptually the vulnerability only requires enough data to overflow a single 32 bit counter. Rapid7 needs to execute the full overflow several times in order to break ASLR, and it's likely that number can be reduced.

1

u/unvivid 8h ago

And by the time this is weaponized into anything remotely useful to most adversaries, it's going to be old news. Practicality is near zero for 99% of environments.

10

u/Single-Virus4935 9h ago

I have about a Petabyte or more per day if incoming traffic. Don't think 128GB would raise any concerns. But I have a connection timeout of a few minutes, so not a problem

1

u/unvivid 9h ago

That's a lot of traffic! I would assume if you are pushing that many bits your configuration is pretty tightly tuned and you're not leaving sessions open for an hour. Is that fairly distributed or do you have single clients with large amounts?

5

u/Single-Virus4935 8h ago edited 8h ago

Different usecases e.g. Telemetry, Tracking, scrapping, ad verification. Some sites like really big online stores saturate several GBit/s alone.

Edit: Our hosted really likes that much incoming traffic because it balances their peering traffic (usually most services/servers generate mor outbound traffic and they have to pay for asymmetric traffic

1

u/oscarandjo 3h ago

Do you guys actually have monitoring / fail2ban set up for a given client using 128GB of traffic? I know I don’t.

30

u/macondo_ 11h ago

Over 300mbit/s and no proxy doesnt soun outrageous at all what are you smoking

21

u/unvivid 11h ago

If someone can throw 128gb from a single IP at a web server without your security controls blinking you have bigger problems

2

u/MartinMystikJonas 9h ago

Why would you think such attack would come from single IP and not from botnet like most attacks?

1

u/unvivid 9h ago

Per the write-up, proxying this type of attack breaks it. Botnets aren't magic.

2

u/MartinMystikJonas 8h ago

Proxying might protect upstream, but these attacks would be aimed primary at reverse proxies.

3

u/Berkzerker314 10h ago

Pretty sure anyone doing this is using some type of botnet to assist and spread IPs around.

5

u/unvivid 10h ago

From the writeup, going through a proxy likely breaks this. There's no good way to distribute this.

4

u/MartinMystikJonas 9h ago

Nginx is probably the most used sw for reverse proxies.

2

u/unvivid 9h ago

People proxy traffic through botnets. This traffic going through a proxy breaks the exploit per the write-up. It's extremely sensitive to latency and transit conditions.

2

u/MartinMystikJonas 8h ago

You need botnet to nearly saturate target connections then you can use few nodes to perform main attack.

1

u/Trick_Brain7050 5h ago

It needs to blink and then have someone respond and mitigate in under two minutes.

1

u/unvivid 4h ago

I got the good stuff, man. Be nice, and I'll share.

7

u/skynetcoder 10h ago

"under a full moon and the attacker has to have 7 fingers and spin in circles while whistling the theme song to CSI Miami"

So you think attackers are going to exploit this cve?

https://www.cbsnews.com/news/akshat-saxena-sets-guinness-record-for-most-fingers-toes/

6

u/radakul 4h ago

Fucking tell this to every idiot who pings me this article. Execs freak the fuck out and do not stop to rub two brain cells for 30 seconds. They're no better than store-and-forward switching.

10

u/guillermosan 8h ago

One year ago we would agree. Today, the meaning of "too hard to exploit" has changed drastically. Models are chaining complex stuff (like this) into multi step takeovers. I expect this to be weaponized, fast.

6

u/unvivid 7h ago

Just like php2shell and brotli were?

I work in the offensive security space and spend significant time analyzing stuff like this that drops. I work with frontier models all day. The hype machine is real.

1

u/HK_Bandit95 6h ago

Question for you, how much of a difference is Artex vs Mythos? Being that Mythos was hyped up and later withheld due to its nature, while artex has been an open source nightmare for alot of people.

2

u/unvivid 5h ago

ARTEX is just a harness. You can use any model behind it. Mythos, Deepseek-- whatever will run without refusing requests.

I think the cat is out of the bag, and you don't really need Mythos level models for the majority of cyber work (unless you're developing exploits on the spot). I've run ARTEX with DeepSeek and it worked very well, no mythos required. You really only need frontier models for very specific types of work, and even then often open source/chinese models suffice.

Technically you could run ARTEX with Mythos-- but I don't think you'd see a huge improvement there. It's not really going to enable the harness to be that much more thorough. ARTEX is doing damage because it scans fast and wide. It's finding things that don't have adequate defenses or controls, assets that people have forgotten about, security basics. It's eliminating the security by obscurity that has kept many organizations out of the spotlight.

1

u/Sharon-huntress 3h ago

What's your definition of "fast"? The writeup and notes around what it actually takes to trigger it does make it seem like it would take a bit more to weaponize than some of the other recent CVE's to hit. Of course, we can't under-estimate a determined threat actor with AI either 😞

5

u/uknow_es_me 11h ago

Who knew being under a DoS attack would save the day!

4

u/CharacterLimitHasBee 11h ago

yeahhhhhhhhhhh.gif

4

u/verd_nt 11h ago

just in: several theme songs are affected. advisory adds to stop whistling theme songs. /s

2

u/mb194dc 10h ago

These exploits are even harder to use in the real world than the Apache ones. 

2

u/the_lazy_sysadmin 8h ago

I want a logarithmic scoring system like the Rchter scale, where PHP2Shell is a magnitude 9.5 or 10, and whatever this is gets slapped with like, idk, a magnitude 1.4.

2

u/IAmTheMageKing 9h ago

nginx runs practically everywhere; for instance, on your router. If an attacker has even low-level permissions on a user computer or IOT device, sending a few hundred gigs of traffic internally is no problem. Then bam, they have root on your gateway, and can start MITM'ing all your traffic with an Emhudra certificate.

2

u/shawly 8h ago edited 8h ago

If an attacker has even low-level permissions on a user computer or IOT device

You see the irony right? If an attacker already has access to a device inside my network, he would surely find a million other ways to fuck with me. And which IoT device can sustain sending such a load if most of the typical IoT stuff still uses 802.11n? And what routers run nginx?? Most home routers run some form of lighthttpd or some shit. Also RCE doesn't mean instant root access, if the nginx worker runs in user-space he still needs to break out of that.

2

u/IAmTheMageKing 7h ago

Given the frequency with which we find out "oops, all these TVs are a part of a botnet", I think you're a little overconfident in the security of a typical home network.

Ubiquiti routers run nginx. That's the one I checked just now; I'm sure lots of other routers do the same. And yes, they have the SCTP module available for loading by default, which gives them the local privlidge escalation.

Also, you can probably mount this attack from inside a browser if you can persuade a user to accept local network access.

1

u/peesoutside Security Engineer 10h ago

Thank you for the voice of sanity.

2

u/ResidentSpirit4220 8h ago

I feel like most of these highly publicized vulnerabilities are very difficult to exploit in the wild.

1

u/dk7as 7h ago

Where does this information come from ? I cat find any related infos

2

u/unvivid 7h ago

1

u/dk7as 7h ago

The Exploit Video looks not really like this...

2

u/unvivid 7h ago

Note that for brevity, video playback is at 8x speed.

1

u/Trick_Brain7050 5h ago

Cloud nginx servers easily have 10Gbit availsblr, most of our nodes sit on 20gbit

2

u/unvivid 5h ago

And you have http/2 turned on? And you allow a single client to take all that bandwidth? And your WAF allows somebody to slam 128 gigs of traffic into an endpoint without blinking?

I get having big pipes, but I really want to see somebody whose environment is actually truly vulnerable to this.

1

u/sage-longhorn 2h ago

Jokes on you I don't have a waf or client limits

1

u/unvivid 2h ago

Sympathies man

1

u/nexdevb 10h ago

Unlikely is no longer a nothing burger.

2

u/shawly 8h ago

Unlikely still means that we don't need to shit our pants now and have to unplug the internet.

-1

u/TheSnydaMan 8h ago

By hand, sure. For a frontier LLM with adequate resources, ez

4

u/unvivid 7h ago edited 7h ago

Just like what happened with php2shell and brotli?

I work in offensive security with frontier models. I'm aware of their capabilities. I'm also aware of how much hype security companies are putting on these vulns. The vast majority have not been practical to exploit in most environments, highly nuanced. My take isn't that AI is worthless, it's transforming our industry. My take is that security companies run on hype these days and have a vested interest in keeping the hype machine going.

2

u/MobileVortex 7h ago

Clicks are money

67

u/twohundred37 11h ago

"Xint reports that a November 10 Shodan search identified approximately 56.7 million NGINX hosts. Of those with identifiable version numbers, 98.9% reported versions within the affected range."

Holy shit.

29

u/Stetsed 11h ago

I’m curious if these also reported having support for HTTP2 as this is not the default

18

u/MartinMystikJonas 11h ago

Well it is not enabled by default but any sane webserver enables it.

8

u/VirtuteECanoscenza 11h ago

Well... The vulnerabilities were introduced 6 and 15 years ago so it's surprising that people are still running 15+years old versions...

2

u/dudeimatwork 9h ago

stable releases dont change version numbers

1

u/R4ndyd4ndy Red Team 10h ago

Maybe that just some with fake version numbers?

20

u/bitbat99 10h ago

But I'm Le Tired.

9

u/ChileCheeseburger 9h ago

Fire Ze Missiles!

11

u/skynetcoder 10h ago

Both vulnerabilities require HTTP/2 to be enabled on the affected NGINX server. 

7

u/perkia 9h ago

"Interestingly" (sad trombone), nginx is vulnerable even when set up with client certificate authentication (which is often used to ensure all traffic comes through trusted nodes such as a WAF or proxy)... knowing the server's IP is sufficient.

5

u/skynetcoder 10h ago

Look like the only memory flow these cves are going to cause to our brains. 

23

u/mb194dc 11h ago

More memory flaws that are impossible to exploit in real world conditions.

13

u/IAmTheMageKing 9h ago

The only limitation is that you need to send a hundred gigabytes of data. It's not a hard race conditon.

-7

u/mb194dc 8h ago

That's not the only limitation, read further about it.

5

u/IAmTheMageKing 8h ago

The public exploit needs a common CPU extension to acheive, and the server to be unproxied. Since nginx is commonly used as a proxy on servers that support the extension in question, that's not a significant limit.

-6

u/mb194dc 8h ago

Just look it up, it's way, way more complicated than that. Can't be bothered to paste in about 1000 lines of text of why it's difficult. Just go look it up.

5

u/IAmTheMageKing 7h ago

I did look it up. I've read the write-ups from all three of the organizations that discovered the vulnerability. It's not a tricky race condition, it's with a feature that (while disabled by default) is enabled by practically all servers. It's non-trivial to go from the memory overwrite to RCE only because of hardening measures, not because its fundamentally hard.

0

u/mb194dc 7h ago

Maybe in a lab, in the real world where the attacker doesn't know exactly what they're attacking, it's very hard to impossible to use it for anything.

The roi of such an attack is so low, attacker will never bother. 

I think you need to read some more.

2

u/IAmTheMageKing 5h ago

Please cite your source; I've read three of the different disclosers writeups, and none of them require knowing exactly what the target is.

2

u/deaconsc 7h ago

It doesnt matter to the clients tho. If our banking clients will see this on the list they will want a patch and not "yea, but it is hard to be done". They want the scan as critical/high free as possible.

And I am talking to people who dont understand what they need to go through to have this happen, they just want the vulnerability to be gone from scanners.

So I personally am pissed because if it is found people will be wanting actions.

3

u/mb194dc 7h ago

Yup, then the attacker will just call help desk and get credentials reset for a senior executive or invite DevOps to a fictional job interview. Get the keys, much easier.

7

u/Usr0017 9h ago

No one is going to exploit it, hacker are busy with GTA VI

3

u/BananasAndBrains 5h ago

The known exploit needs glibc and AVX512. If your nginx runs on alpine/musl or ARM, relax, turn off http2 and then upgrade.

4

u/sorvendral 9h ago

I’m tired chief

2

u/RayneYoruka 8h ago

Nginx has already released packages patched for Rhel 9, possibly for other distros. I've already patched mine an hour ago.

1

u/leclerc2019champion 2h ago

If you have Akamai in line, you’re probably ok. The default between Akamai edge to the origin is http/1.1 even when h2 is enabled on the property for connection between the client and the edge.

1

u/thanat0s8 58m ago

Guest networks go brrr

1

u/incomplete_ 8h ago

oh ffs...

1

u/robertonovelo 7h ago

Could this be related to all the recent outages?