<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Heap-Overflow on Aretiq AI</title><link>https://aretiq.ai/tags/heap-overflow/</link><description>Recent content in Heap-Overflow on Aretiq AI</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 25 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://aretiq.ai/tags/heap-overflow/index.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-9256 — NGINX ngx_http_rewrite_module Overlapping PCRE Captures Heap Buffer Overflow RCE</title><link>https://aretiq.ai/research/vul260525-cve-2026-9256-nginx-ngx-http-rewrite-module-overlapping-pcre-captures-heap-buffer-overflow-rce/</link><pubDate>Mon, 25 May 2026 00:00:00 +0000</pubDate><guid>https://aretiq.ai/research/vul260525-cve-2026-9256-nginx-ngx-http-rewrite-module-overlapping-pcre-captures-heap-buffer-overflow-rce/</guid><description>&lt;h2 id="1-overview">1. Overview&lt;/h2>
&lt;p>A heap buffer overflow vulnerability exists in the NGINX &lt;code>ngx_http_rewrite_module&lt;/code> when processing rewrite directives that use overlapping Perl-Compatible Regular Expression (PCRE) capture groups with a redirect or query-string replacement. When a rewrite rule like &lt;code>^/((.*))$&lt;/code> produces multiple captures referencing the same URI content and the replacement string references both captures (e.g., &lt;code>$1$2&lt;/code>), the buffer allocation underestimates the space needed for URI-escaped output, leading to a heap overflow in the worker process. An unauthenticated remote attacker can send crafted HTTP requests containing URI characters that require escaping (such as &lt;code>+&lt;/code>) to crash the NGINX worker process or potentially achieve remote code execution. The vulnerability provides both a controlled heap write primitive and an information disclosure primitive — the overflow causes adjacent heap data (including pool pointers) to leak into the HTTP response, enabling ASLR bypass. Combined with the attacker-controlled overflow content and nginx&amp;rsquo;s deterministic pool allocator, this creates a viable path to code execution. F5/NGINX addressed this vulnerability in nginx 1.31.1 (mainline) and 1.30.2 (stable), released May 22, 2026.&lt;/p></description></item></channel></rss>