[Security] NGINX HTTP/2 and HTTP/3 vulnerabilities (CVE-2026-123633, CVE-2026-123007 and CVE-2026-121810): Snowplow collectors are not exploitable

Last updated: November 18, 2026

[18-Nov-2026]

Several critical vulnerabilities in NGINX were disclosed this week (Wiz advisory). This notice covers three of them:

  • CVE-2026-123633 and CVE-2026-123007, in NGINX's HTTP/2 handling. They could allow an unauthenticated attacker to execute code on a server running an affected NGINX version, but only when HTTP/2 is enabled in NGINX.

  • CVE-2026-121810, in NGINX's HTTP/3 (QUIC) handling. It can only be reached when HTTP/3 is enabled in NGINX.

All three are fixed upstream in NGINX 1.30.7 (stable) and 1.31.9 (mainline).

CVE-2026-123634, published in the same advisory, is fixed in the same NGINX release. We are confirming whether it applies to Snowplow collectors and will update this notice.

We have had questions from several customers, so this notice sets out our position and what to expect from security scanners.

Is Snowplow affected?

Snowplow-managed collectors on AWS are not exploitable through CVE-2026-123633, CVE-2026-123007 or CVE-2026-121810. The collector servers run an NGINX version that scanners flag, but neither HTTP/2 nor HTTP/3 is enabled in it:

  • The collector's NGINX configuration doesn't enable HTTP/2 or HTTP/3, and no configuration option turns either on.

  • The AWS load balancer in front of the collector handles HTTP/2 connections from your trackers and forwards requests to NGINX over HTTP/1.1. If you test the public collector endpoint, the HTTP/2 response you see comes from the load balancer, not from NGINX.

  • HTTP/3 runs over UDP. The collector servers only accept TCP traffic, and only from the load balancer, so there is no route for HTTP/3 to reach NGINX.

  • We have verified this in the configuration used by every Snowplow-managed collector and on live collectors, where NGINX only accepts HTTP/1.1.

The vulnerable code paths can't be reached, so no configuration change is needed, and there is no reason to stop or pause a pipeline. Event collection is unaffected.

Area

Status

Collector servers (AWS)

Not exploitable: HTTP/2 and HTTP/3 not enabled. Patched NGINX to follow

Collector application

Not affected: the Collector application image doesn't include NGINX

Snowplow Mini (Swagger UI)

Being removed: Mini is end of life

What about Snowplow Mini?

Some scanners report these vulnerabilities on a path called /swagger-ui. These findings most likely come from the Swagger UI container bundled with Snowplow Mini. Snowplow Mini reached end of life on 11 November 2026 and won't receive this or any future fix, so we are removing remaining Mini instances. Customers with a live Mini have been contacted directly. Snowplow Micro is the replacement. More details are in the Snowplow Mini sunset notice.

If your Mini has already been removed, a fresh scan should no longer show the /swagger-ui findings. If it still does, please raise a ticket with the resource or instance ID from your scanner and we'll check it.

Do I need to do anything?

If Snowplow manages your pipeline: no. No action is needed on your side.

If you run Snowplow components in your own infrastructure: these vulnerabilities affect NGINX, not Snowplow software. If you run NGINX in front of your collector or any other service, check whether HTTP/2, HTTP/3 or a resolver is configured:

nginx -T 2>/dev/null | grep -nE 'http2|http3|quic|resolver'

If any of these appear, upgrade NGINX to 1.30.7 or 1.31.9 (or later). Until you can:

  • HTTP/2: set http2 off; in each server block on NGINX 1.25.1 or later, or remove http2 from the listen lines on older versions.

  • HTTP/3: remove the quic parameter from the listen lines and any http3 on; directives, and stop advertising HTTP/3 to clients (for example, an Alt-Svc header that mentions h3).

Then run nginx -t and nginx -s reload.

A note for security scanners

Scanners identify these vulnerabilities by the NGINX package version installed on the collector server, not by its configuration. They will continue to report CVE-2026-123633, CVE-2026-123007 and CVE-2026-121810 on Snowplow collector servers until the patched NGINX package is rolled out, even though HTTP/2 and HTTP/3 are not enabled. This is expected.

Your scanner may also list other recent NGINX CVEs against the same package. The patched NGINX roll-out is intended to cover every NGINX CVE your scanner reports on Snowplow collector servers. We will roll it out as part of the managed service, and we will update this notice when that happens.

Questions

If you have any questions, or your security team needs a formal response for a supplier assessment, please raise a ticket with Snowplow Support and reference this notice.