Menu

The nginx HTTP/2 CVEs are out, OpenResty isn't patched yet: how we shipped the fix in a day (and the `| tee` bug that hid our updates)
📰

The nginx HTTP/2 CVEs are out, OpenResty isn't patched yet: how we shipped the fix in a day (and the `| tee` bug that hid our updates)

DEV Community: security·Jikwang Moon·about 22 hours ago
#f4ggrtSp
#devtosecurity#devto#dev#nginx#openresty
Long article (954 words) — no AI summary yet.
Reading 0:00
15s threshold

On November 18 nginx published a batch of security fixes, headed by two HTTP/2 bugs rated CVSS 9.2:

memory corruption in HTTP/2 flow control (CVE-2026-123007) and a use-after-free when HTTP/2 is used

with proxying (CVE-2026-123633). Wiz showed unauthenticated remote code execution

against a default HTTPS + HTTP/2 setup. Everything up to nginx 1.31.8 is affected; 1.31.9 and 1.30.7 are fixed.

If you build on OpenResty , there's a catch: the current release, 1.31.8.1, bundles nginx 1.31.8,

and there is no patched OpenResty release yet. That's our situation with

Corvus , an open-source gateway built on OpenResty. This is

what we did, so you can do the same for your own OpenResty builds.

1. Check what actually applies to you

The advisory list for that day has more than ten

entries.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.