NGINX HTTP/2 fixes: what Shopify app teams should check
NGINX shipped fixes on 18 November 2026 for two HTTP/2 vulnerabilities that app teams should check before Black Friday traffic rises. The relevant question for a Shopify business is whether its own…
NGINX shipped fixes on 18 November 2026 for two HTTP/2 vulnerabilities that app teams should check before Black Friday traffic rises. The relevant question for a Shopify business is whether its own app servers, middleware or externally hosted storefront components run an affected NGINX build.
NGINX’s advisory list identifies CVE-2026-123007, a memory-corruption flaw in HTTP/2 flow control, and CVE-2026-123633, an HTTP/2 use-after-free. It lists 1.30.7 and 1.31.9 as fixed versions for both. The affected ranges begin at 1.9.5 and 1.19.7 respectively, through 1.31.8; the fixed stable branch is an exception to that broad version range.
What is exposed?
Wiz’s research describes unauthenticated remote code execution when HTTP/2 is enabled, with additional conditions differing between the bugs. It demonstrated the flow-control issue against a server delivering static files, so an application does not need a separate coding flaw to be exposed.
Severity terminology differs: Wiz rates both critical at CVSS 4.0 9.2, while the NGINX list labels the flow-control issue major and the use-after-free medium. The practical action is to match the deployment against the vendor advisories and install the appropriate fix.
A useful inventory for commerce teams
Start with the systems your team operates: reverse proxies in front of public app endpoints, webhook services, fulfilment connectors and self-hosted content sites. This disclosure alone does not establish that Shopify’s hosted storefront or checkout is compromised. Ask managed providers for their deployment-specific status rather than assuming every service shares your configuration.
For each affected host, record its owner, exposed endpoints, running build and patch status. Distribution packages may backport fixes, so check the distributor’s security notice as well as the version string. Rebuild pinned containers and verify that the replacement is actually serving traffic.
Wiz recommends temporarily disabling HTTP/2 if an immediate upgrade is impossible: on supported releases, set http2 off; and remove the http2 parameter from listen directives, test compatibility, reload and confirm old workers have exited. Follow the full advisory for your configuration. Investigate unexpected worker crashes or commands; those are warning signs, not proof of compromise.
An IP allowlist and a patched server address different risks. If an allowed server is compromised, its permitted network address does not make its requests trustworthy. Keep evidence of the deployment review alongside your app-security checks.
20 November update: what the Cloudflare proxy protects
Cloudflare’s technical analysis distinguishes the client-facing HTTP/2 and HTTP/3 paths from other NGINX exposure. An origin reachable only through Cloudflare’s HTTP proxy benefits from the edge terminating those client connections. A directly reachable origin bypasses that protection.
This is not a blanket exemption from patching: resolver and mail configurations have different attack paths. Inventory the modules and listeners actually enabled, restrict direct origin access where appropriate, install the relevant vendor-fixed package and restart the affected service. Upstream fixed releases include NGINX 1.30.7 and 1.31.9; distribution backports require checking the vendor’s package advisory rather than comparing version strings alone.
More from News
See all →