Security Resilience

CVE-2026-123007

Memory Safety in F5 Dos 4.5.0 – 4.7.0

Public PoCMemory Safety
Published
18 November 2026
Modified
20 November 2026
Patch / advisory
CVSS Score v4 9.2
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.060 94th percentile
Risk Priority 44 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-123007 is a critical-severity Wrap or Wraparound (CWE-191) vulnerability in F5 Dos. Its CVSS base score is 9.2 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 6% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

Advisories

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-19186Shared CWE-191, CWE-787
CVE-2026-78011Shared CWE-191, CWE-787
CVE-2026-29078Shared CWE-191, CWE-787
CVE-2026-120058Shared CWE-191, CWE-787
CVE-2026-116569Shared CWE-191, CWE-787
CVE-2023-33059Shared CWE-191, CWE-787
CVE-2026-65704Shared CWE-191, CWE-787
CVE-2026-64009Shared CWE-191, CWE-787
CVE-2026-45813Shared CWE-191, CWE-787
CVE-2023-32653Shared CWE-191, CWE-787

Affected Assets

f5
dos
4.5.0 — 4.7.0
f5
nginx gateway fabric
1.5.0 — 1.6.2 · 2.0.0 — 2.9.0
f5
nginx ingress controller
3.7.1, 3.7.2, 4.0.0, 4.0.1 · 5.0.0 — 5.8.0 · 2026-lts-r1 — 2026-lts-r11
f5
nginx instance manager
2.19.0 — 2.25.0
f5
nginx open source
1.9.5 — 1.30.7 · 1.31.0 — 1.31.9
f5
nginx plus
r34, r35, r36 · 37.0.0 — 37.0.8.1 · 37.1.0 — 37.3.0.1
f5
waf
4.12.0 — 4.16.0 · 5.4.0 — 5.8.0 · 5.9.0 — 5.16.2
redhat
3scale api management platform
2.0
redhat
hardened images
all versions
redhat
enterprise linux
10.0, 8.0, 9.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and static/dynamic analysis directly find integer underflow defects before code is released.

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

Security engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer underflow during subtraction.

Input validation can reject or sanitize values that would cause a subtraction to underflow the representable range.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.PS-06 full match
blocks

Secure SDLC practices directly prevent integer underflow defects via input validation, bounds checking, and static analysis.

ID.RA-01 partial match
blocks

Vulnerability scanning and code analysis can surface underflow flaws after they are introduced.

PR.PS-02 partial match
blocks

Routine patching can remediate known underflow bugs once they are discovered in deployed software.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

finds

Security testing in development catches integer underflow defects before release.

prevents

Training developers in secure coding practices (bounds checking, safe memory handling) reduces some out-of-bounds write instances, but the defect requires deep technical knowledge and even trained developers make these mistakes, so only a minority of instances are prevented.

prevents

Secure coding standards directly prescribe safe integer handling and overflow/underflow prevention.

prevents

A.8.30’s contractual secure-design, coding, and testing requirements reduce the introduction of integer-underflow defects in outsourced software, but fallible implementation practice leaves a substantial remainder.

finds

A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw. Integer underflow is primarily a first-party code defect discoverable by static analysis or code review, which A.8.8 does not reach. A.8.8 finds this weakness only where it has been published as a CVE in a third-party component, which is a minority of latent instances.

References