<?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 kalfaoglu.net</title><link>https://blog.kalfaoglu.net/tags/heap-overflow/</link><description>Recent content in Heap-Overflow on kalfaoglu.net</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 26 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.kalfaoglu.net/tags/heap-overflow/index.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-42533: Critical nginx Heap Overflow — Patch Now</title><link>https://blog.kalfaoglu.net/posts/2026-07-26-cve-2026-42533-nginx-heap-overflow-en/</link><pubDate>Sun, 26 Jul 2026 00:00:00 +0000</pubDate><guid>https://blog.kalfaoglu.net/posts/2026-07-26-cve-2026-42533-nginx-heap-overflow-en/</guid><description>&lt;p&gt;F5 patched &lt;a href="https://nvd.nist.gov/vuln/detail/CVE-2026-42533"&gt;CVE-2026-42533&lt;/a&gt; on July 15. If you run nginx, this one deserves your attention before the proof-of-concept code drops — and there is a countdown on that.&lt;/p&gt;
&lt;h2 id="what-the-flaw-is"&gt;What the flaw is&lt;/h2&gt;
&lt;p&gt;The vulnerability is a heap buffer overflow (CWE-122) in nginx&amp;rsquo;s script engine — the component that assembles output strings from configuration directives at request time. It surfaces under a specific configuration pattern: a &lt;code&gt;map&lt;/code&gt; block using regex matching, where the map&amp;rsquo;s output variable appears in a string expression &lt;em&gt;after&lt;/em&gt; a numbered capture variable (&lt;code&gt;$1&lt;/code&gt;, &lt;code&gt;$2&lt;/code&gt;) from an earlier regex match.&lt;/p&gt;</description></item></channel></rss>