Nginx Open SourceWeb server / proxy · F5
CVE-2024-35200
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWhen NGINX Plus or NGINX OSS are configured to use the HTTP/3 QUIC module, undisclosed HTTP/3 requests can cause NGINX worker processes to terminate.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a denial-of-service vulnerability in NGINX (both OSS and Plus) when configured with the HTTP/3 QUIC module. Specific undisclosed HTTP/3 requests can trigger a crash causing NGINX worker processes to terminate unexpectedly.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Nginx Open SourceWeb server / proxy
>= 1.25.0, < 1.26.1
Nginx PlusWeb server / proxy
= r30= r31
FedoraOperating system
= 39= 40CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify NGINX versionRun `nginx -v` or `nginx -V 2>&1` to get the installed versionAffected if Version is >= 1.25.0 and < 1.26.1 for OSS, or r30/r31 for Plus, or from Fedora 39/40 packages
-
Verify QUIC module is compiled inRun `nginx -V 2>&1` and look for `--with-http_v3_module` in the configure argumentsAffected if The --with-http_v3_module flag is present, indicating QUIC/HTTP3 support was built
-
Check if QUIC is enabled in configurationInspect nginx.conf and included files for the `quic` parameter on `listen` directives (e.g., `listen 443 quic;`)Affected if Any server block contains a listen directive with the `quic` parameter enabled
-
Identify active QUIC-related directivesSearch configuration files for `quic_bind`, `quic_retry`, or `quic_hec` directivesAffected if Any QUIC-specific configuration directives are present and active
User is affected only if running a vulnerable NGINX version AND the HTTP/3 QUIC module is both compiled in and actively configured via listen quic directives.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.26.1
If HTTP/3 QUIC is not required, disable the quic module in NGINX configuration. Otherwise, monitor for NGINX security advisories for the patch and apply it once available.
Nginx Open Source: 1.26.1 or later; Nginx Plus: r32 or later
- 1. Identify the installed nginx version using 'nginx -v' or 'nginx -V'
- 2. For Nginx Open Source: Upgrade to version 1.26.1 or later from the official nginx repository (nginx.org/en/download.html)
- 3. For Nginx Plus: Upgrade to r32 or later from F5's download portal (my.f5.com)
- 4. For Fedora systems: Update via 'sudo dnf update nginx' to receive the patched package for Fedora 39 or 40
- 5. After upgrade, reload nginx configuration using 'nginx -s reload' or restart the service
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Nginx Open Source
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-35200 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-35200 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data