Skip to main content
Menu
CVEs

F5 NGINX Plus memory corruption in mail proxy module

Affects NGINX Plus and NGINX Open Source when configured as a mail proxy. Fixed in NGINX Plus 37.0.8.1 and 37.3.0.1, and NGINX Open Source 1.30.7 and 1.31.9.

CVE-2026-113425EUVD-2026-128948GHSA-RMPV-V5M5-RR27Published November 18, 2026, updated Needs attention

8.1HighCNA
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

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.

Written by a model

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.

Who should check

Teams running NGINX Plus or NGINX Open Source configured as a mail proxy

“When NGINX Plus or NGINX Open Source is configured as a mail proxy”

cert-portal.siemens.com

What to do

  1. Upgrade to a fixed version: NGINX Plus 37.3.0.1, 37.0.8.1 · NGINX Open Source 1.31.9, 1.30.7.

  2. 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-20):
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.
Conditions (all must be true for the bug to be hit):
- Configured as an NGINX Plus or NGINX Open Source mail proxy (source: https://cert-portal.siemens.com/productcert/html/ssa-935812.html)
- Code execution additionally requires ASLR to be disabled or bypassed by the attacker (source: https://cert-portal.siemens.com/productcert/html/ssa-935812.html)
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://cert-portal.siemens.com/productcert/html/ssa-935812.html
- 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"}.

Affected versions

cve.now Index

65of 100 · methodology v3
  • 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

Timeline

  1. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  2. CVE published
  3. First seen by cve.now
  4. Posted on X by cve.now
  5. cve.now early warning

    F5 discloses NGINX HTTP/2 flaw CVE-2026-123007 that can allow code execution

  6. Exploit code on GitHub

    LLCForge/CVE-2026-113425

    2 days
  7. Record last updated1 day
  8. EPSS reached 10%

    FIRST estimates at least a 10% chance of exploitation in the next 30 days

Public exploit activity

10Posted on X by cve.now100%0Nov 18Nov 22
  • GitHub PoC repos: 1
  • EPSS: 13.9%
  • Posted on X by cve.now Nov 18

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

On X 10

Evidence 5

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-113425
RecordNVD · CVE-2026-113425
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · LLCForge/CVE-2026-113425 · Repository
Other links 2
Patchmy.f5.com · manage/s/article/K000163931
Linkcert-portal.siemens.com · productcert/html/ssa-935812.html

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). Its EPSS score, the predicted chance of exploitation in the next 30 days, reached 10% or higher on 2026-11-21.

Source: cve.now feed data

What does this mean?

A remote unauthenticated attacker may crash an NGINX worker process or corrupt its memory, disrupting service. Remote code execution is a potential impact, but the advisory says it applies only on systems with ASLR disabled or when the attacker can bypass ASLR.

Source: cert-portal.siemens.com, cve.org

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

Am I affected, and how do I check?

Only NGINX configured as a mail proxy is affected. The listed ranges are NGINX Plus 37.0.0 before 37.0.8.1, NGINX Plus 37.1.0 before 37.3.0.1, NGINX Plus R33 (the advisory lists no fixed release for this line), NGINX Open Source 1.30.0 before 1.30.7, NGINX Open Source 1.31.0 before 1.31.9, and NGINX Open Source 0.5.33 onward. To check, run nginx -v for the version and look for a mail block in the nginx configuration.

Source: cert-portal.siemens.com, cve.org

How do I fix CVE-2026-113425?

Upgrade NGINX Plus to 37.0.8.1 or 37.3.0.1, or NGINX Open Source to 1.30.7 or 1.31.9. Until the upgrade, restrict listeners to trusted networks.

Source: cert-portal.siemens.com, cve.org

No corrections so far. Something wrong on this page? Report an error.