Skip to content

WebCritical 9.2Patch available

CVE-2026-121810

HTTP/3 use-after-free in NGINX allows remote DoS and possible RCE

How scary is it?

updated 20 Nov 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • Yes

    Reachable over the network1

    Can be attacked remotely (CVSS AV:N).

  • Yes

    Proof-of-concept code is public2

    1 GitHub proof of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list3

    Not in the catalog as of our last sync.

Scare-o-meter

Act this week

Serious and within reach of attackers. Schedule the fix this week.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: Public proof-of-concept code exists for a network-reachable flaw; CVSS 9.2.1 Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run one of these 2 products in an affected versionF5 NGINX Open Source / F5 NGINX Plus

    F5 NGINX Open Source: >= 1.31.0 and < 1.31.9, >= 1.30.0 and < 1.30.7, >= 1.25.09 and < *

    F5 NGINX Plus: >= 37.1.0 and < 37.3.0.1, >= 37.0.0 and < 37.0.8.1, >= R33 and < *

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. An attacker can reach it over the network

    CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.

    Source 1

  3. Specific conditions are met that the attacker does not control

    CVSS attack complexity: High (AC:H). Needs specific conditions, a race or a particular configuration. The CVE record does not always say which.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per our analysisA patch is available

    The CVE record we hold states no fixed release number. See the advisories in the references.

    See the references

  2. Recommendation, AI-writtenDisable HTTP/3 / block QUIC traffic and apply vendor patch when released.

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

Major vulnerability. NGINX is widely deployed; this CRITICAL HTTP/3 use-after-free can cause DoS and possible RCE, impacting internet-facing infrastructure across organizations.

CVSS
9.2Criticalscored by the publisher (CNA)
Exploited in the wild
Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
EPSS
16.4%chance of exploitation in the next 30 daystop 3% of scored CVEsFIRST score of 21 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
18 Nov 2026analysed here 19 Nov 2026

Summary

Impact

Remote unauthenticated DoS via worker crash; potential remote code execution if ASLR is disabled or bypassed.

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
No. See why

Executive summary (AI-written)

CVE-2026-121810 presents a significant risk to organizations using NGINX Plus and NGINX Open Source configurations that implement HTTP/3. With a CVSS score of 8.1, this vulnerability allows remote, unauthenticated attackers to create a use-after-free condition in the NGINX worker process, potentially leading to service disruptions and denial-of-service (DoS). The likelihood of exploitation increases in environments where Address Space Layout Randomization (ASLR) is disabled, making certain systems particularly vulnerable. While there is currently no published patch, organizations must remain vigilant as the absence of remedial measures can lead to severe business interruptions and impact operational continuity.

Technical analysis (AI-written)

In summary, understanding the implications of CVE-2026-121810 is crucial for security professionals. Given its potential to disrupt essential services and the complexity of exploitation, organizations are encouraged to adopt robust operational security practices to mitigate risks while keeping abreast of updates from NGINX regarding remediation and best practices.

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources.

Affected products

ProductAffected versions
F5 NGINX Open Source>= 1.31.0 and < 1.31.9>= 1.30.0 and < 1.30.7>= 1.25.09 and < *Vendor says fixed in: not stated
F5 NGINX Plus>= 37.1.0 and < 37.3.0.1>= 37.0.0 and < 37.0.8.1>= R33 and < *Vendor says fixed in: not stated

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • NGINX Open Source (HTTP/3 enabled)
  • NGINX Plus (HTTP/3 enabled)

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? No. This is a use-after-free memory bug. Generic WAF rules do not recognise the input that triggers it; only a rule written for this specific CVE can, and only if the triggering request has a recognisable shape.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept
CISA SSVC
exploitation none, automatable no, technical impact totalAssessed by CISA 18 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 18 Nov 2026First proof-of-concept repository on GitHub (unvetted)
  2. 18 Nov 2026CISA SSVC assessment: exploitation nonesame day later
  3. 18 Nov 2026Published1 day later
  4. 19 Nov 2026CVE record last updated1 day later
  5. 19 Nov 2026Analysed by vulneraibility.comsame day later

Common questions

Is CVE-2026-121810 being exploited?

Not confirmed. CVE-2026-121810 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 16% probability of exploitation in the next 30 days.

How severe is CVE-2026-121810?

CVE-2026-121810 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-121810?

Yes. A fix has been recorded for CVE-2026-121810. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-121810 affect?

CVE-2026-121810 affects NGINX Open Source (HTTP/3 enabled), NGINX Plus (HTTP/3 enabled). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-121810?

Disable HTTP/3 / block QUIC traffic and apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

1 reference in the CVE record, grouped by the tags the record gives them.

Patches (1)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.