<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Node2shell on Anaz Haidhar</title>
    <link>https://anazhd.com/tags/node2shell/</link>
    <description>Recent content in Node2shell on Anaz Haidhar</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>© 2026 Anaz Haidhar</copyright>
    <lastBuildDate>Fri, 23 Oct 2026 22:00:00 +0800</lastBuildDate><atom:link href="https://anazhd.com/tags/node2shell/index.xml" rel="self" type="application/rss+xml" />
    
    <item>
      <title>Node2Shell: Node.js Brotli RCE CVE-2026-111497, PoC Status and Fixes</title>
      <link>https://anazhd.com/posts/nodejs-brotli-rce-cve-2026-111497/</link>
      <pubDate>Thu, 22 Oct 2026 18:27:55 +0800</pubDate>
      
      <guid>https://anazhd.com/posts/nodejs-brotli-rce-cve-2026-111497/</guid>
      <description>&lt;p&gt;I just wrote about &lt;a href=&#34;https://anazhd.com/posts/php2shell-cve-2026-109618-109619/&#34; &gt;PHP2Shell and PHP&amp;rsquo;s request-lifecycle bugs&lt;/a&gt;. Now Node.js has its own runtime security update to deal with. Different engine, different failure mode, same uncomfortable reminder: safe-looking application code still depends on native code underneath it.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>
