CVE-2026-97205· CVE.org (no NVD analysis yet)· CNA f5

NGINX ngx_http_core_module vulnerability

Noroxi assessment

Priority: Monitor (action score 36/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 0.48% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: azl3 httpd 2.4.68-1 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to azl3 httpd 2.4.68-1 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_core_module module. When asynchronous file I/O (AIO) is enabled in certain configurations, processing a Server Side Includes (SSI) page containing “include virtual” commands may trigger a Use-After-Free (UAF) in the NGINX worker process. This may cause memory corruption or a worker process crash. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system, corrupt its memory, or possibly trigger code execution. 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.

CriticalCVSS 9.2 · v4.0—Proof of concept Fix available

Published: Oct 14, 2026
Updated: Oct 15, 2026
EPSS: 0.4% · 40th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 36 / 40 · 9.2 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.4%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · f5: 8.1; NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Using nginx plus? Add it to your stack and be the first to know about CVEs like this one. (Nginx)

Is nginx on your server exposed to the internet?

The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.

Run a port scan

Versions reported by the vendor

Affected version ranges reported by the assigning authority (f5). Independent of NVD's CPE analysis and usually ahead of it.

F5 NGINX Open Source
- 1.31.0 and later · before 1.31.7affected
- 1.30.0 and later · before 1.30.6affected
F5 NGINX Plus
- 37.1.0 and later · before 37.1.0.1affected
- 37.0.0 and later · before 37.0.5.1affected
- R36 and lateraffected
- R35 and lateraffected
- R34 and lateraffected
- R33 and lateraffected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Alpine:v3.24	nginx	before 1.30.6-r0	1.30.6-r0
Debian:12	nginx	from 0	—
Debian:13	nginx	before 1.26.3-3+deb13u10	1.26.3-3+deb13u10
Debian:14	nginx	before 1.30.4-8	1.30.4-8
openSUSE:Tumbleweed	nginx	before 1.31.7-1.1	1.31.7-1.1
Red Hat:hummingbird:1	nginx	before 0:1.30.6-1.hum1	0:1.30.6-1.hum1
Red Hat:hummingbird:1	nginx-all-modules	before 0:1.30.6-1.hum1	0:1.30.6-1.hum1
Red Hat:hummingbird:1	nginx-core	before 0:1.30.6-1.hum1	0:1.30.6-1.hum1
Red Hat:hummingbird:1	nginx-filesystem	before 0:1.30.6-1.hum1	0:1.30.6-1.hum1
Red Hat:hummingbird:1	nginx-mod-devel	before 0:1.30.6-1.hum1	0:1.30.6-1.hum1
Red Hat:hummingbird:1	nginx-mod-http-geoip	before 0:1.30.6-1.hum1	0:1.30.6-1.hum1
Red Hat:hummingbird:1	nginx-mod-http-image-filter	before 0:1.30.6-1.hum1	0:1.30.6-1.hum1
Red Hat:hummingbird:1	nginx-mod-http-perl	before 0:1.30.6-1.hum1	0:1.30.6-1.hum1
Red Hat:hummingbird:1	nginx-mod-http-xslt-filter	before 0:1.30.6-1.hum1	0:1.30.6-1.hum1
Red Hat:hummingbird:1	nginx-mod-mail	before 0:1.30.6-1.hum1	0:1.30.6-1.hum1
Red Hat:hummingbird:1	nginx-mod-stream	before 0:1.30.6-1.hum1	0:1.30.6-1.hum1
Red Hat:hummingbird:1	nginx-mod-stream-geoip	before 0:1.30.6-1.hum1	0:1.30.6-1.hum1

Same product

f5: all records

Other highest-scoring records for the same primary product.

CVE-2026-27654NGINX ngx_http_dav_module vulnerability
43Plan
CVE-2026-93479NGINX map directive and regex matching vulnerability
36Monitor
CVE-2026-15176NGINX ngx_http_core_module vulnerability
36Monitor

Published before and after this one in the same product

← EarlierCVE-2026-90439Sep 15, 2026 · NGINX ngx_http_v3_module vulnerability
27Monitor
← EarlierCVE-2026-95101Oct 14, 2026 · NGINX ngx_http_v3_module vulnerability
27Monitor
Later →CVE-2026-97629Oct 14, 2026 · NGINX ngx_http_ssl_module vulnerability
33Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
azl3 httpd 2.4.68-1 on Azure Linux 3.0	Release Notes	Microsoft (MSRC)
alpine:nginx	1.30.6-r0 · Alpine:v3.24	Package registry (OSV)
debian:nginx	1.26.3-3+deb13u10 · Debian:13	Package registry (OSV)
debian:nginx	1.30.4-8 · Debian:14	Package registry (OSV)
opensuse:nginx	1.31.7-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
red hat:nginx	0:1.30.6-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-all-modules	0:1.30.6-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-core	0:1.30.6-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-filesystem	0:1.30.6-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-devel	0:1.30.6-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-http-geoip	0:1.30.6-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-http-image-filter	0:1.30.6-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-http-perl	0:1.30.6-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-http-xslt-filter	0:1.30.6-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-mail	0:1.30.6-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-stream	0:1.30.6-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:nginx-mod-stream-geoip	0:1.30.6-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:0	2026-10-15

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedOct 14, 2026
First PoCOct 15, 2026same day
Fix recordedOct 17, 2026+3 d
TodayOct 24, 2026+9 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

F5 acknowledges Cyberlanc3r for bringing this issue to our attention and following the highest standardscoordinated disclosure.reporter

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Noroxi's write-up

Our blog post on this record: impact, how to check your site and the upgrade steps.

CVE-2026-97205: nginx use-after-free with AIO and SSI. Is your server affected?

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: None
Scope: X

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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/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

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Oct 17, 2026, 3:32 AM UTC
Exploit maturitynone → pocOct 16, 2026, 3:36 AM UTC
SSVC exploitation— → noneOct 15, 2026, 5:07 AM UTC
Exploit maturity— → noneOct 14, 2026, 4:08 PM UTC
CVSS8.1 → 9.2Oct 14, 2026, 4:07 PM UTC
Severityhigh → criticalOct 14, 2026, 4:07 PM UTC

For records you follow, these changes also arrive as notifications. →

References

my.f5.com/manage/s/article/K000162608

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records

Noroxi analysis

What does it mean in your environment?

We use this product, ask for help

Data sources and verification

CNA: f5

CVE.org (CNA)Oct 15, 2026, 10:31 AM UTC
CISA ADPOct 15, 2026, 10:31 AM UTC
NVDOct 15, 2026, 11:18 AM UTC
FIRST EPSSOct 22, 2026, 12:00 AM UTC
OSV / GHSAOct 23, 2026, 3:18 AM UTC
MSRCOct 23, 2026, 3:25 AM UTC
PoC-in-GitHubOct 23, 2026, 3:18 AM UTC

Each line is when that source was last processed for this record.

NGINX ngx_http_core_module vulnerability

Noroxi assessment

Get told when this record changes

Follow CVE-2026-97205

What does it mean in your environment?

Affected systems

Is your version affected?

Watch new CVEs for nginx plus

Versions reported by the vendor

Package-level exposure

Same product

Remediation

Which version to upgrade to

Exploit status

Research context

Timeline

Patch and commit links

Credits

Variant candidates

Chain candidates

Noroxi's write-up

Technical details

Attack conditions

If successful

Root cause

The bug in code

Attack context

Change log

References