<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Http2 on Kuldeep Pisda</title><link>https://kdpisda.in/tag/http2/</link><description>Recent content in Http2 on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 15 Nov 2026 08:30:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/http2/index.xml" rel="self" type="application/rss+xml"/><item><title>Node's November Security Release: Where TLS Terminates Decides Your Exposure</title><link>https://kdpisda.in/nodejs-november-2026-security-release-tls-termination-exposure/</link><pubDate>Sun, 15 Nov 2026 08:30:00 +0530</pubDate><guid>https://kdpisda.in/nodejs-november-2026-security-release-tls-termination-exposure/</guid><description>&lt;p&gt;Node.js released &lt;a href="https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"&gt;22.23.5, 24.22.3 and 26.13.1&lt;/a&gt; on November 11 with fixes for 16 CVEs. Most of the coverage leads with the count and the HTTP/2 crashes. The detail that decides how urgent this release is for you is one sentence at the end of the worst advisory, CVE-2026-123864: &amp;ldquo;Cleartext &lt;code&gt;node:http&lt;/code&gt; is not affected.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;That bug lets an unauthenticated client read memory belonging to other connections, &amp;ldquo;including TLS private keys and other users&amp;rsquo; requests.&amp;rdquo; It only exists when Node itself is the TLS server. The same is true for three more of the high and medium issues in this release. So before reading 16 advisories, answer one question about each service: does the process that runs &lt;code&gt;https.createServer()&lt;/code&gt;, &lt;code&gt;tls.createServer()&lt;/code&gt; or &lt;code&gt;http2.createSecureServer()&lt;/code&gt; face clients, or does something in front of it terminate TLS?&lt;/p&gt;</description></item></channel></rss>