Sébastien Rigaux

Tech watch

← All links

CVE

A standardized identifier system for publicly referencing cybersecurity vulnerabilities.

Black image with Vercel’s white triangular logo, the text “VERCEL CHANGELOG,” the date “01.26.2026,” and the title “Summary of CVE-2026-23864”.

CVE-2026-23864 covers multiple denial-of-service vulnerabilities in React Server Components. Specially crafted HTTP requests to Server Function endpoints can cause a server crash, an out-of-memory exception, or excessive CPU use. Vercel says the flaws do not allow remote code execution.

Vercel deployed protective rules to its WAF, but recommends upgrading immediately: patched React releases start at 19.0.4, 19.1.5, and 19.2.4. The page also lists patched Next.js releases and says other affected frameworks should be updated using their maintainers’ guidance.

Josh Story, Jimmy Lai, Andy RianchoFound via bytes.dev

Node.js graphic on a brown hexagonal-pattern background, showing the logo and the text “Node.js — Wednesday, November 11, 2026 Security Releases”.

Node.js security updates fix CVEs ranging from low to high severity across the 22.x, 24.x and 26.x release lines. Several HTTP/2 and TLS flaws can crash a server or expose memory; others affect mTLS authentication, certificate validation and the Permission Model.

The advisories spell out exploitation conditions, including TLS session reuse across different certificate policies and HTTP/2 data queued without being charged to maxSessionMemory. Fixed versions are Node.js v22.23.5, v24.22.3 and v26.13.1.

@nodejsFound via This week in React

Red and black cve.now graphic for CVE-2026-126187 showing critical severity 9.5, remote code execution in Server Components, a public exploit, and fixed versions.

CVE-2026-126187 describes an unauthenticated remote code execution flaw in some React Server Components setups. The listed fixed versions are 19.0.9, 19.1.10, 19.2.9, and 19.3.1.

Exposure requires vulnerable versions of react-server-dom-webpack, -parcel, or -turbopack, React code running on a server, and an RSC-supporting framework, bundler, or plugin. The described scenario is extremely rare: a response must carry multiple typed arrays and an attacker-controlled value. Public exploit code exists; no confirmed attacks are reported.