Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-9256: Heap buffer overflow in NGINX ngx_http_rewrite_module

Published May 22, 2026 · Updated 14 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days8 mentions · peak 5 in a dayToday
CVSS9.2Critical · v4
EPSS10.9%96th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendors
Debian ProjectRed HatF5
IdentifiersCVE-2026-9256CWE-122 · Heap-based Buffer Overflow

CVE-2026-9256 is a heap-based buffer overflow in ngx_http_rewrite_module affecting NGINX Plus and NGINX Open Source. The vulnerability occurs when a rewrite directive uses distinct, overlapping Perl-Compatible Regular Expression (PCRE) capture groups and its replacement string references multiple overlapping captures in a redirect or arguments context. An unauthenticated remote attacker can submit crafted HTTP requests that, subject to additional conditions beyond the attacker's control, corrupt heap memory in an NGINX worker process. Exploitation can cause worker termination and restart, resulting in denial of service. Code execution is also possible when Address Space Layout Randomization (ASLR) is disabled or bypassed. Versions beyond End of Technical Support were not evaluated.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation can crash and restart NGINX worker processes, disrupting HTTP service availability. If ASLR is disabled or bypassed, the heap corruption may permit arbitrary code execution in the worker process context, potentially compromising the confidentiality and integrity of data accessible to that process as well as service availability. Code execution does not inherently confer root privileges.

Mitigation

If you can’t patch tonight, do this now.

Remove or rewrite affected rewrite directives so that redirect or arguments replacement strings do not reference multiple distinct, overlapping PCRE capture groups. Maintain ASLR: it reduces the stated code-execution risk but does not prevent the heap overflow or denial of service. Where configuration changes or patching cannot be performed immediately, restrict untrusted network access to affected HTTP services. The Tanzu buildpack advisories list no product-specific workaround.

Remediation

Patch, then assume compromise.

Install the applicable vendor-supported NGINX security update. Fixed Debian packages are 1.22.1-9+deb12u8 for Debian 12 and 1.26.3-3+deb13u6 for Debian 13. For the specified RHEL support streams, fixed package releases are 1.20.1-14.el9_2.7 under RHSA-2026:93472, 1.20.1-16.el9_4.7 under RHSA-2026:93468, and 1.20.1-22.el9_6.7 under RHSA-2026:93467; use these or later vendor-approved fixed releases for the corresponding stream. Affected VMware Tanzu deployments should update NGINX Buildpack to 1.2.87 or Staticfile Buildpack to 1.6.82, as applicable. Upstream NGINX Plus and Open Source fixed version numbers are not specified here; select the update appropriate to the installed product and supported release.

Public exploits

Exploits

3 exploits validated by Mallory's analysis. Hidden: 6 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-9256-PocThis repository is a real exploit/PoC set for a heap buffer overflow in nginx's ngx_http_rewrite_module caused by undercounting escaped output size when nested overlapping regex capture groups are referenced multiple times in a static rewrite target. The repo is small and purpose-built: three Python PoCs (heap_leak.py, libc_leak.py, crash_verify.py), a Docker lab environment under env/, and a detailed README explaining root cause, trigger conditions, and expected results. Exploit capability is staged rather than full end-to-end RCE. Stage 1 (heap_leak.py) sends crafted HTTP GET requests to /echo/%25...A and parses reflected query output to recover heap pointers from ngx_http_script_engine_t fields such as e->ip, e->sp, and e->request. Stage 2 (libc_leak.py) targets /leak2/%25...A and relies on proxy_pass plus add_header to surface raw overflow bytes in the X-Leak-Y response header, scanning for a 0x7f... pointer consistent with a libc-region address; this requires ASLR to be disabled for reliability. Stage 3 (crash_verify.py) targets /leak9/ with a deeply nested capture pattern and a controlled number of encoded '+' characters to produce a larger overflow that corrupts heap metadata and crashes the nginx worker, confirming DoS. The included nginx.conf is central to the exploitability: it defines the vulnerable rewrite routes, an internal backend on 127.0.0.1:19322 for the proxy_pass leak stage, and tuning such as request_pool_size 7920 to make the overwrite deterministic. The Dockerfile and compose file create a reproducible lab based on nginx:1.31.0, exposing port 19321 and optionally allowing ASLR-disabled execution via setarch in entrypoint_aslr_off.sh. Overall, this is an operational exploit lab demonstrating unauthenticated remote web-triggered memory corruption in nginx, with practical primitives for heap disclosure, libc-range disclosure, and worker crash/DoS. It does not include a final shell or command-execution payload, but it clearly aims to support exploit development toward code execution under favorable memory-layout conditions.3nou9h · Disclosed May 28, 2026 · markdown · python · web · networkOperationalNginx-chain-Rift-PoolslipRepository is a compact, self-contained exploit lab for chaining two nginx rewrite-engine vulnerabilities into ASLR-independent remote command execution against stock official nginx:1.30.0. Structure is simple: README.md documents the chain and usage; nginx.conf defines the intentionally vulnerable target configuration; run.sh launches a Dockerized nginx lab and a slow local upstream; exp_official.py performs the exploit. The main exploit logic is in exp_official.py. It first abuses the /search rewrite path to trigger the PoolSlip over-read and recover leaked heap/libc pointers from the reflected degraded search response. It then computes libc base, heap base, and libc system(). Next it uses repeated POST requests to /api/upload to spray heap chunks containing fake cleanup records and a command buffer. It opens and times multiple TCP connections to groom nginx connection pools, then sends a crafted GET to /api/v1/... to trigger the rift overflow and partially overwrite the low 2 bytes of a limit_conn cleanup pointer with URL-safe bytes only. Finally, by closing/freeing connections in a controlled order, nginx walks the corrupted cleanup list during pool destruction and invokes system(cmd). The exploit is operational rather than a mere PoC: it contains full leak, address derivation, heap spray, grooming, overwrite, and trigger stages, with a user-supplied command via --cmd. It is not framework-based. The target is specifically nginx OSS on Linux, demonstrated on Debian/glibc 2.41 in the official nginx:1.30.0 container. Fingerprintable target routes are /search, /lookup, /api/v1, /api/upload, and /healthz, with local upstreams at 127.0.0.1:8080 and 127.0.0.1:9200 in the lab.y198nt · Disclosed Jun 5, 2026 · markdown · python · network · webOperationalCVE-2026-9256-POCThis repository is a small standalone proof-of-concept for CVE-2026-9256, described as an Nginx heap buffer overflow. It contains four files: a minimal README, a docker-compose file to launch a reproducible Nginx 1.30.1 environment, a custom nginx.conf that defines the suspected vulnerable rewrite behavior, and a Python PoC script. The exploit logic is entirely in poc.py. The script targets http://localhost:8080 and sends crafted GET requests with paths made of repeated '+' characters. In leak_heap(), it sends a shorter payload, disables redirect following, and inspects the returned Location header for hexadecimal values matching pointer patterns (0x...). In crash(), it sends a larger payload intended to trigger a crash, treating request failure/exception as success. The nginx.conf is central to the exploit setup: requests to '/' are rewritten using the regex ^/((.*))$ into /redirect/$1$2? with an HTTP redirect, which may cause malformed handling of attacker-controlled URI data and expose memory contents in the redirect header or trigger memory corruption. Overall, this is a network/web-targeted PoC for local reproduction and validation of information disclosure and denial-of-service behavior, not a full weaponized exploit and not tied to a larger exploitation framework.06-ux · Disclosed Jun 3, 2026 · markdown · yaml · network · webPoC
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Debian ProjectDebian Linuxoperating_system
F5Dosapplication
F5Nginxapplication
F5Nginx Gateway Fabricapplication
F5Nginx Ingress Controllerapplication
F5Nginx Instance Managerapplication
F5Nginx Plusapplication
F5Wafapplication
Red HatDiscoveryapplication
Red HatHardened Imagesapplication
Red HatRed Hat Enterprise Linuxoperating_system
Red HatUpdate Infrastructureapplication
FAQ

Frequently asked questions

Is CVE-2026-9256 exploited in the wild?
As of Nov 5, 2026, Mallory has no reports of CVE-2026-9256 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-9256?
Yes. Mallory tracks 3 public exploits or proofs of concept for CVE-2026-9256, the earliest disclosed May 28, 2026.
Is there a patch for CVE-2026-9256?
Install the applicable vendor-supported NGINX security update. Fixed Debian packages are 1.22.1-9+deb12u8 for Debian 12 and 1.26.3-3+deb13u6 for Debian 13.
What products are affected by CVE-2026-9256?
F5 Nginx, F5 Nginx Plus, Debian Project Debian Linux, Red Hat Discovery, F5 Dos, and 7 more.
How severe is CVE-2026-9256?
CVE-2026-9256 has a CVSS v4 score of 9.2 (Critical) and an EPSS score of 10.9% (96th percentile) as of Nov 5, 2026.
Activity feed

Recent activity

82 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
tenable nessus pluginsNews · Nov 2, 2026RHEL 9 : nginx (RHSA-2026:93468) | Tenable®A vulnerability in nginx's ngx_http_rewrite_module that can cause code execution or denial of service. The advisory provides updated RHEL nginx packages. The CVSS exploit-maturity metrics attributed to this CVE indicate exploit availability; the Nessus check relies on self-reported version information rather than testing exploitation.Read more ↗tenable nessus pluginsNews · Nov 2, 2026RHEL 9 : nginx (RHSA-2026:93472) | Tenable®A vulnerability in nginx's ngx_http_rewrite_module allows code execution and denial of service. The advisory identifies affected RHEL 9 packages and provides security updates. Nessus detects exposure using reported package versions rather than exploitation testing.Read more ↗redhat accessNews · Nov 2, 2026RHSA-2026:93472 - Security Advisory - Red Hat Customer PortalA vulnerability in nginx's ngx_http_rewrite_module that can cause code execution and denial of service. Red Hat advisory RHSA-2026:93472 provides fixes in nginx package release 1.20.1-14.el9_2.7 for affected Red Hat Enterprise Linux 9.2 offerings. The advisory rates the update Important but does not describe exploitation prerequisites.Read more ↗redhat accessNews · Nov 2, 2026RHSA-2026:93468 - Security Advisory - Red Hat Customer PortalA vulnerability in nginx's ngx_http_rewrite_module that can allow code execution and denial of service. Red Hat advisory RHSA-2026:93468 includes a fix in nginx-1.20.1-16.el9_4.7 for the listed Red Hat Enterprise Linux 9.4 products. The advisory rates the overall update Important.Read more ↗
+23 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity42Community discussion across Reddit, Mastodon, and other social sources.