Patch tracker / CVE reference / CVE-2026-123007

CVE-2026-123007

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 vu...

Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.

Vulnerability, CVSS 8.1 (High).

How to fix CVE-2026-123007What the press saysAdmin questions

Risk summary

High
8.1
CVSS v3 base
High
Severity
Not listed
Actively exploited
Schedule normally
No exploitation observed as of 2026-11-20: not in the CISA KEV catalog, and EPSS has not scored it yet.
No vendor fix is mapped yet. This page refreshes daily and will name the patch the day one is published.
Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Updated November 19, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Senserva AI Opinion and rich prompt for CVE-2026-123007

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

From the Senserva blog

How to fix CVE-2026-123007

Apply the patched version named in the vendor security advisory. Where a workaround exists, apply it only until the update is deployed, not as a substitute.

Common questions about CVE-2026-123007

Is CVE-2026-123007 actively exploited?

It is not currently listed in the CISA Known Exploited Vulnerabilities catalog. That can change: unexploited CVEs regularly get weaponized months after disclosure, which is why patching on your normal cadence matters.

What fixes CVE-2026-123007?

The authoritative fix is in the vendor security advisory. Apply the patched version listed there; the references below link to the CVE record and NVD detail.

Which products are affected by CVE-2026-123007?

See the vendor security advisory for the affected product list.

Can I ask my own AI about CVE-2026-123007?

Yes. This page includes a free, ready-to-paste AI prompt with CVE-2026-123007's key facts: severity, CVSS, CISA KEV status, and the affected products. Copy it into Claude, ChatGPT, or Copilot for a triage plan.

Scope and sources

Authoritative references

Every Microsoft CVE and the patches that fix it, ranked by real-world risk: the Microsoft Patch Tracker. The full searchable CVE reference: CVE and vulnerability management.

New to a term on this page? CVE, KB, KEV, CVSS, and EPSS are each explained once, on the Senserva security lexicon. Reference: Microsoft CVE and vulnerability management and the Microsoft patching guide.
All information provided as is, without warranty; verify against the vendor advisory before acting. All information and usage is subject to the Senserva EULA. Data notice and terms.