Yesterday nginx shipped fixes for a flaw in how it tracks HTTP/2 flow control. Security firm Wiz reports that it could let an unauthenticated attacker run code on a server. Below you can break a toy counter yourself, replay the second bug step by step, and check your own version.
HTTP/2 lets each side say how many bytes the other may send before waiting. Each stream starts with a window of 65,535 bytes (RFC 9113). The server subtracts every chunk it sends. This is a toy model, not nginx's code.
Guess first. A counter that can only hold 0 to 4,294,967,295 sits at 0 and loses 1. What does it show?
The second flaw (CVE-2026-123633) is a use-after-free. Wiz describes the chain below. Step through it, then switch on the fix and run it again.
Type the version from nginx -v, for example 1.24.0. The ranges come from nginx.org. A flaw only matters when its feature is switched on.
| CVE | Where | Affected | Needs |
|---|
Wiz advises upgrading, and as a stopgap on nginx 1.25.1 or later setting http2 off; in affected server blocks, then re-enabling HTTP/2 after the upgrade. Linux distributions often backport fixes without changing the version number, so also check your vendor's advisory.
Real exploitation needs more than a wrong counter, and Wiz reports it can defeat ASLR. These models only show why the bug classes are dangerous. Both were found with AI assistance according to Wiz: its researchers say AI models make it practical to trace the subtle memory paths that hid these flaws, which is the claim of one vendor and not independently confirmed here.