Security / News explained
nginx’s HTTP/2 fixes belong below the request filter
nginx 1.30.7 and 1.31.9 fix a group of vulnerabilities, including two HTTP/2 memory issues. Request filters cannot substitute for patching the component that processes the protocol.
nginx released stable version 1.30.7 and mainline version 1.31.9 on November 18, 2026. The release fixes several vulnerabilities across protocol and module paths. Two of them, CVE-2026-123007 and CVE-2026-123633, concern memory safety while handling HTTP/2. [1]
AWS’s November 19 bulletin makes an important boundary explicit: these HTTP/2 issues can occur before a complete HTTP request exists. AWS WAF managed rules and custom request rules therefore cannot effectively detect or block them. [6]
That is a useful distinction for anyone who normally answers an urgent web advisory by asking for a filtering rule. A request policy can examine information available at its own stage of processing. It cannot retroactively protect an earlier component that has already mishandled the protocol. The layer where a fault happens determines where a repair has to reach.
Two paths, with different conditions
For CVE-2026-123007, F5’s CNA record describes HTTP/2 flow control exceeding its allowed threshold, potentially causing a heap buffer overflow and worker crash. It also identifies possible remote code execution when address-space randomization is disabled or an attacker can bypass it. The issue concerns the traffic-processing data plane, without control-plane exposure. [3]
CVE-2026-123633 has a different condition. F5 describes a use-after-free when nginx accepts HTTP/2 client connections, proxies requests to a backend, and the worker is running low on connection capacity. The record again qualifies possible code execution by the address-space-randomization condition. [4]
Those prerequisites matter when explaining the findings. They also do not turn a connection-limit adjustment into a documented software fix. Our reading is that capacity observations can help an operator understand the affected path, while the vendor’s corrected release remains the repair. A quieter graph is welcome; it is not a patch receipt.
The nginx security page traces these paths back to 1.9.5 for flow control and 1.19.7 for the use-after-free. On current upstream branches, the CNA records identify earlier 1.30.x and 1.31.x releases as affected, with stable 1.30.7 and mainline 1.31.9 correcting both issues. [2] [3] [4]
Find the component that speaks HTTP/2
Imagine a hypothetical application where a public reverse proxy accepts HTTP/2 and forwards ordinary HTTP/1.1 requests to the application server. Looking only at the application server’s protocol settings would answer the wrong question. The public listener is the component processing those client connections, so its software and configuration belong in the assessment.
The same reasoning applies to a bundled proxy in an application image or an ingress deployment. A product inventory that merely says “nginx present” gives too little detail. The useful connection is between the listener’s actual protocol, the nginx build serving it and the party responsible for replacing that build.
The November 18 release also addresses resolver, HTTP/3, TLS request-body handling, mail proxy and other module issues. An HTTP/2 assessment is therefore a focused part of the release review, not a claim that disabling one protocol resolves every vulnerability in the package. [1]
AWS says Elastic Beanstalk’s default nginx configuration does not enable HTTP/2; the relevant exposure concerns environments where customers enabled it on their own listener. Its bulletin points to the available platform correction. The November 19 platform release notes independently identify the nginx security update. [5] [6]
Availability and completion are separate facts
The AWS bulletin also reports corrected nginx packages for Amazon Linux 2, Amazon Linux 2023 and Amazon Linux 2027. Package availability describes what an operator can install. It does not establish that a particular instance, image or environment has already received the correction. [6]
In a hypothetical release report, “new image built” and “all public workers replaced” could both be accurate updates at different times. Treating them as the same milestone would hide the remaining work. A useful completion record identifies the deployed build and explains which serving processes have moved to it, alongside normal application-health checks.
For the affected custom Elastic Beanstalk listeners, AWS identifies disabling HTTP/2 as an interim mitigation until the patch can be applied. That is scoped guidance for these HTTP/2 paths, with the broader release’s other fixes still relevant. [6]
Application access logs also need careful interpretation. A lack of unusual completed requests cannot, by itself, prove that a problem occurring before request completion was never reached. This is a reason to keep the investigation’s observation limits visible, without inventing an attack from an unexplained crash or a vulnerability announcement.
The practical decision is concrete: connect the advisory to the listener that processes the protocol, then connect the available correction to the build that is serving traffic. Request filtering still has its place. For these flaws, the vendor’s explanation puts the repair earlier in the conversation.
Sources + further reading
Source dates describe the original material. Publication above is the date this Zyel article went live.
- nginx November 18 release announcementnginx · Checked Nov 20, 2026
- nginx security advisories and affected version rangesnginx · Checked Nov 20, 2026
- CVE-2026-123007 F5 CNA recordF5 · Checked Nov 20, 2026
- CVE-2026-123633 F5 CNA recordF5 · Checked Nov 20, 2026
- Elastic Beanstalk Amazon Linux 2023 platform release, November 19AWS · Checked Nov 20, 2026
- AWS nginx security bulletin 2026-192AWS · Checked Nov 20, 2026
Reader discussion
What would you ask next?
Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.
No reader comments yet.