CVE
F5 NGINX Plus memory corruption in mail proxy module
- Exploited
- Public exploit code, no confirmed attacks
- Fix
- Fixed in NGINX Plus 37.3.0.1, 37.0.8.1 · NGINX Open Source 1.31.9, 1.30.7
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: NGINX Plus 37.3.0.1, 37.0.8.1 · NGINX Open Source 1.31.9, 1.30.7.
Summary
NGINX Plus and NGINX Open Source, when configured as a mail proxy, contain a use-after-free bug that a remote attacker can trigger over the network without logging in. Successful exploitation may crash an nginx worker process or corrupt its memory, disrupting service, and remote code execution is a potential impact.
Original description
When NGINX Plus or NGINX Open Source is configured as a mail proxy, undisclosed traffic can cause a use-after-free in an nginx worker process. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.
Impact: A remote unauthenticated attacker may crash an nginx worker process or corrupt its memory, disrupting service. Remote code execution is a potential impact. 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.
cve.now Index
- Exploitation22/40Public exploit on Exploit-DB or GitHub
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach17/20Affects nginx (a widely deployed server, runtime, framework or database)
- Severity9.1/10CVSS 8.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 88 if added to CISA KEV
- Would score about 83 if CISA's SSVC rates exploitation active
- Would score about 70 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: NGINX Plus 37.3.0.1, 37.0.8.1 · NGINX Open Source 1.31.9, 1.30.7.
Workaround: Restrict listeners to trusted networks.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-113425 (NGINX ngx_mail_proxy_module vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-113425 (entry last updated 2026-11-18):
Affected:
- F5 NGINX Plus: from 37.1.0, fixed in 37.3.0.1; from 37.0.0, fixed in 37.0.8.1; from R33
- F5 NGINX Open Source: from 1.31.0, fixed in 1.31.9; from 1.30.0, fixed in 1.30.7; from 0.5.33
Fixed versions: 37.3.0.1, 37.0.8.1, 1.31.9, 1.30.7.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Restrict listeners to trusted networks. (source: https://www.cve.org/CVERecord?id=CVE-2026-113425)
CISA KEV: CVE-2026-113425 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-113425 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://my.f5.com/manage/s/article/K000163931
- https://www.cve.org/CVERecord?id=CVE-2026-113425
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-113425
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-113425"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- cve.now early warning
F5 discloses NGINX HTTP/2 flaw CVE-2026-123007 that can allow code execution
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
- Exploit code on GitHub
LLCForge/CVE-2026-113425
Affected versions
- F5 NGINX Plus
From 37.1.0 · fixed in 37.3.0.1; From 37.0.0 · fixed in 37.0.8.1; From R33
- F5 NGINX Open Source
From 1.31.0 · fixed in 1.31.9; From 1.30.0 · fixed in 1.30.7; From 0.5.33
Evidence 4
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-113425 |
| Record | NVD · CVE-2026-113425 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · LLCForge/CVE-2026-113425 · Repository |
| Other links 1 | |
| Patch | my.f5.com · manage/s/article/K000163931 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-113425
Is CVE-2026-113425 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data
Which versions are affected by CVE-2026-113425?
NGINX Plus: from 37.1.0 before 37.3.0.1; from 37.0.0 before 37.0.8.1; from R33. NGINX Open Source: from 1.31.0 before 1.31.9; from 1.30.0 before 1.30.7; from 0.5.33.Source: cve.now feed data
How do I fix CVE-2026-113425?
Upgrade to the fixed version on the same release branch: NGINX Plus 37.3.0.1 or 37.0.8.1, or NGINX Open Source 1.31.9 or 1.30.7. If an upgrade is not possible yet, restrict listeners to trusted networks.Source: cve.org