Vulnerability report

No Exploitation Yet

CVE-2026-123007

NGINX ngx_http_v2_module vulnerability

F5 / NGINX Plus · affected before 37.3.0.1

Severity
CVSS 9.2 · Critical
Confidence
—
Exploit status
PoC Available
EPSS
—
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2026-123007 is an unauthenticated NGINX ngx_http_v2_module vulnerability affecting F5 NGINX Plus, NGINX Open Source. This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2.

Have exploitation attempts been observed?

Previdian records an exploitation-related signal (poc available). This CVE has not been added as a known exploited vulnerability.

Who is affected?

F5 / NGINX Plus and NGINX Open Source, including affected before 37.3.0.1, affected before 37.0.8.1, and affected before *.

What should we do?

Track for updates. Assess relevance to your asset inventory and enrichment workflows.

Overview

This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2

This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2. When NGINX processes undisclosed traffic, the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.

Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or potentially execute code remotely. There is no control plane exposure; this is a data plane issue only.

Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

F5 Affected
NGINX Plus
Before 37.3.0.1 Before 37.0.8.1 Before *
F5 Affected
NGINX Open Source
Before 1.31.9 Before 1.30.7 Before *
View vendor advisory (opens in new tab)
Published
18 Nov 2026
Exploitation date
—
Attack vector
Remote
Complexity
High
Privileges
None
User interaction
None

CVE References

Exploitation evidence

Exploitation evidence for this CVE

These signals relate to exploitability. Previdian has not added this CVE as a known exploited vulnerability.

Proof of concept available

GitHub

Recorded 18 Nov 2026

Public scanner or PoC coverage increases practical exploitability.

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

Risk and context

Severity, weaknesses, and research context

CVSS v4.0

9.2 Critical

Potential damage if exploited. Separate from whether attackers are using it.

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

EPSS

—

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Recent mention · TheRegister

AI found more critical bugs in another widely used technology running 225M websites

Open source NGINX joins patchapalooza

Read full advisory

All CVSS Scores

CVSS v4.0 9.2 Critical

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS v3.1 8.1 High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

All Mentions

Recent mention · TheRegister

AI found more critical bugs in another widely used technology running 225M websites

TheRegister · 18 Nov 2026

Open source NGINX joins patchapalooza

Recent mention · CERT-EU

2026-022: Critical vulnerabilities in Nginx

CERT-EU · 18 Nov 2026

On 18 November 2026, F5 published an advisory addressing five vulnerabilities in NGINX that allow an unauthenticated remote attacker to execute code with the privileges of the NGINX worker process. While researchers managed to successfully demonstrate the use of CVE-2026-123007, no exploitation in the wild has been reported yet. It is recommended to swiftly update NGINX as soon as possible, prioritising internet facing appliances.

Recent mention · F5 Security Advisories

K000164058: Out-of-band Security Notification (November 18, 2026)

F5 Security Advisories · 18 Nov 2026

Security Advisory Description On November 18, 2026, F5 announced the following security issues. This document is intended to serve as an index of these vulnerabilities to help determine the impact to your F5 devices. You can find the details of each issue in the associated articles. Article (CVE) Affected products K000163925: NGINX resolver vulnerability CVE-2026-123634 NGINX Plus, NGINX Open Source K000163926: NGINX ngx_http_v2_module vulnerability CVE-2026-123007 NGINX Plus, NGINX Open Source K000163927: NGINX ngx_http_v3_module vulnerability CVE-2026-121810 NGINX Plus, NGINX Open Source...

Recent mention · CERT Polska

Krytyczne podatności w serwerze nginx umożliwiające zdalne wykonanie kodu - nginx2root

CERT Polska · 18 Nov 2026

Zespół CERT Polska ostrzega przed pięcioma krytycznymi podatnościami w serwerze nginx, nazwanymi przez ich znalazców nginx2root.Najpoważniejsza z nich, CVE-2026-123007, pozwala nieuwierzytelnionemu atakującemu na zdalne wykonanie poleceń na serwerze z włączonym protokołem HTTP/2 i w domyślnej konfiguracji - z uprawnieniami procesu workera nginx.Podatne są wszystkie oficjalne wydania nginx od 1.9.5 do 1.31.8 włącznie. Wykorzystanie podatności może nie pozostawiać śladów w logach.Poprawka dla wszystkich pięciu luk znajdzie się w wydaniu 1.31.9, zapowiedzianym na 19 listopada 2026 r.Podatności...

Recent mention · NCSC Security Advisories

NCSC-2026-0506 [1.00] [H/H] Kwetsbaarheden verholpen in NGINX door F5 Networks

NCSC Security Advisories · 18 Nov 2026

F5 Networks heeft meerdere kwetsbaarheden verholpen in NGINX Plus en NGINX Open Source. De kwetsbaarheden betreffen verschillende onderdelen en configuraties van NGINX. De belangrijkste kwetsbaarheid met kenmerk CVE-2026-123007 stelt kwaadwillenden in staat om willekeurige code uit te voeren op het onderliggende systeem. Het NCSC verwacht dat er op korte termijn proof of concept code beschikbaar komt, waarna exploitatie op grote schaal verwacht wordt.

Recent mention · Wiz

Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007

Wiz · 18 Nov 2026

Two critical HTTP/2 flaws can allow attackers to compromise NGINX servers, putting the websites, APIs, and sensitive data they handle at risk.

Recent mention · F5 Security Advisories

K000163926: NGINX ngx_http_v2_module vulnerability CVE-2026-123007

F5 Security Advisories · 18 Nov 2026

Security Advisory Description This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2. When NGINX processes undisclosed traffic, the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. (CVE-2026-123007) Impact An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or...

Recent mention · Rapid7

CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED)

Rapid7 · 18 Nov 2026

OverviewToday, both Rapid7 and F5 are disclosing CVE-2026-123007, a critical integer underflow vulnerability affecting nginx HTTP/2, which can allow for unauthenticated remote code execution (RCE) against affected servers under certain conditions.CVE IDDescriptionCWECVSSv4CVE-2026-123007HTTP/2 flow-control memory corruption permitting worker-context RCECWE-191 (Integer Underflow)9.2 (Critical)nginx can miscalculate how much response data an HTTP/2 client has allowed it to send. A remote, unauthenticated client can exploit this error by cancelling queued response data, then make nginx use an...

Recent mention · The Hacker News

10-Year-Old NGINX HTTP/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers

The Hacker News · 18 Nov 2026

Swati KhandelwalNov 18, 2026Vulnerability / Web Security A flaw in NGINX's HTTP/2 support can allow an attacker to run code on servers with HTTP/2 enabled, without needing to log in. The decade-old flaw, CVE-2026-123007, dubbed "nginx2root," has been present in NGINX's open-source code since version 1.9.5, released on September 22, 2015. Fixed versions 1.31.9 and 1.30.7 came out today. F5, the company behind NGINX, says attackers can run code where ASLR is turned off or can be bypassed. Security researchers at Wiz said they bypassed ASLR and ran code through the flaw in tests. Xint's...

Potential Proof of Concepts

These PoCs are unverified and could contain malware. Use at your own risk.

arkrwn/NGINX2Root-CVE-2026-123007

github · Created 2026-11-18 20:00:12 UTC · 0 stars · AI assessment 91%

sfewer-r7/CVE-2026-123007

github · Created 2026-11-18 11:16:51 UTC · 0 stars · AI assessment 96%

This repository contains proof-of-concept (PoC) scripts for CVE-2026-123007.

Timeline

From disclosure to today

  1. 15:23 UTC

    CVE published

    Vulnerability disclosed publicly

  2. 11:16 UTC

    Public PoC available

    Public proof-of-concept code published

  3. 18:42 UTC

    CVE ID reserved

    Identifier reserved by the CNA

API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/enterprise/kevs/CVE-2026-123007

Sample API response
{
  "cve_id": "CVE-2026-123007",
  "confidence": null,
  "cvss_score": 9.2,
  "cvss_estimated": false,
  "epss_score": null,
  "exploit_status": {
    "exploited_in_the_wild": false,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}