Node.js: HTTP Defenses Restored and Live Process Probing

Main regained its protection against HTTP response mix-ups from CVE-2026-105481, while HTTP/2 closed memory and truncation gaps. QUIC leak and data-loss fixes, plus live-process inspection and threadpool observability, round out a reliability-focused day.

Duration: PT2M56S

Episode overview

This episode is a short developer briefing from Node.js.

It explains recent repository work in plain language.

  • Show: Node.js
  • Published: 2026-11-17T14:06:08Z
  • Audio duration: PT2M56S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good morning, it's Tuesday, November 17th, 2026, and this is your Node.js briefing.

The headline is reliability under load: the main branch regains a critical HTTP safety check, while HTTP/2 closes two ways a slow or hostile peer could corrupt data or exhaust memory.

First, connection reuse. PR 67073 forward-ports the fix for CVE-2026-105481 to the current agent code. The issue was a kept-alive socket being handed to the next request even though the previous response had already arrived in the operating system buffer, letting one response bleed into another. The fix checks the…

Related HTTP/2 hardening follows the same pattern. PR 67361 enforces the max session memory limit for client requests. Previously only peer-opened streams were checked, so a client whose socket stopped draining could keep queuing requests without bound. Now only the over-limit request fails with a new session-memory…

Second, QUIC is getting sturdier. PR 66730 fixes a per-session security object leak of roughly ten to thirty kilobytes on every connection. PR 66759 fixes lost stream endings when a packet was full of acknowledgments and retransmissions. Together with work to share the stream writer logic in PR…

Thi…

Nearby episodes from Node.js

  1. Crash, Hang and Stream Reliability Fixes
  2. HTTP/2 Stream Fixes, QUIC Hardening, and Performance Wins
  3. TLS Lockdown and Native Crash Fixes
  4. Deprecations Turn Into Errors
  5. Boundary Fixes and Test Runner Hardening
  6. Weekly Recap - Module Cleanup and Leaner Streams
  7. Loaders Removed, Crypto Hardened, I/O Fixed
  8. Teardown Reliability and Stream Memory Fixes