# CVE · Tech watch

[Canonical source](<https://sebastien.rigaux.be/en/tech-watch/tags/cve>)

A standardized identifier system for publicly referencing cybersecurity vulnerabilities.

Related tags : [Security](<https://sebastien.rigaux.be/en/tech-watch/tags/security>)

## [React and Next.js: patch CVE-2026-23864 DoS flaws](<https://sebastien.rigaux.be/en/tech-watch/links/react-and-nextjs-patch-cve-2026-23864-dos-flaws>)

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.

2026-11-16 · [Markdown](<https://sebastien.rigaux.be/en/tech-watch/links/react-and-nextjs-patch-cve-2026-23864-dos-flaws.md>) · [Original resource](<https://vercel.com/changelog/summary-of-cve-2026-23864>)

## [Node.js CVEs fixed in the 22.x, 24.x and 26.x lines](<https://sebastien.rigaux.be/en/tech-watch/links/nodejs-cves-fixed-in-the-22x-24x-and-26x-lines>)

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.

2026-11-15 · [Markdown](<https://sebastien.rigaux.be/en/tech-watch/links/nodejs-cves-fixed-in-the-22x-24x-and-26x-lines.md>) · [Original resource](<https://nodejs.org/en/blog/vulnerability/november-2026-security-releases?ck_subscriber_id=2550494205&utm_source=convertkit&utm_medium=email&utm_campaign=This%20Week%20In%20React%20%23305%3A%20X%2C%20Forms%2C%20e18e%2C%20Next.js%2C%20TanStack%20Start%2C%20Storybook%2C%20MobX%2C%20Zustand%2C%20XState%20%7C%20Exact%2C%20Discord%2C%20Shopify%2C%20Expo%20Modules%2C%20Audio%20API%2C%20Bottom%20Sheet%2C%20Keychain%2C%20Gesture%20Handler%20%7C%20Node.js%2C%20Safari%2C%20Rolldown%2C%20Playwright%20-%2024146776>)

## [React: CVE-2026-126187 puts Server Components at RCE risk](<https://sebastien.rigaux.be/en/tech-watch/links/react-cve-2026-126187-puts-server-components-at-rce-risk>)

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.

2026-11-11 · [Markdown](<https://sebastien.rigaux.be/en/tech-watch/links/react-cve-2026-126187-puts-server-components-at-rce-risk.md>) · [Original resource](<https://cve.now/CVE-2026-126187>)
