--- title: "Dev digest: React and Next.js RCE fixes, Opus 5.5 fast mode" description: "Next.js news for 11 to 18 Oct 2026: patch React and Next.js for three critical RCEs, fast mode for Claude Opus 5.5 leaves preview and Python on Vercel goes GA." canonical_url: "https://www.outofplace.space/blog/dev-digest-2026-10-18" language: "en" last_updated: "2026-10-18" alternates: pl: "https://www.outofplace.space/pl/blog/nowosci-web-dev-2026-10-18.md" --- # Dev digest: React and Next.js RCE fixes, Opus 5.5 fast mode > Next.js news for 11 to 18 Oct 2026: patch React and Next.js for three critical RCEs, fast mode for Claude Opus 5.5 leaves preview and Python on Vercel goes GA. Published 2026-10-18 · Category: AI for developers · Tags: Next.js, React, Claude The week's Next.js news is a security patch: on 14 October 2026 React shipped 19.0.9, 19.1.10, 19.2.9 and 19.3.1 to fix a critical remote code execution in React Server Components, and Next.js shipped 16.4.1 and 15.5.28 for three advisories of its own, two of them critical. Upgrade to Next.js 16.4.2 (or 15.5.28) and the matching React patch before anything else on this list. On the Claude side, fast mode for Claude Opus 5.5 left research preview on 15 October, and the same day Python on Vercel became generally available. The Next.js team also showed how v0 kept Partial Prefetching from multiplying requests, the trade-off we measured in [our Next.js prefetch benchmark](https://www.outofplace.space/blog/nextjs-prefetch-benchmark). | Item | Version or date | What to do | | ----------------------------------- | -------------------- | --------------------------------------------------------------- | | React Server Components advisories | 19.0.9 to 19.3.1 | Upgrade now if any React code runs on a server | | Next.js security release | 16.4.1, 15.5.28 | Upgrade now; only the image RCE has a workaround | | Next.js patch | 16.4.2, 15 Oct | Take it with the security fixes | | Partial Prefetching in v0 | 16 Oct | Read before switching prefetching on for large grids | | Python on Vercel | GA, 15 Oct | Python backends can sit in the same project as the frontend | | AI Gateway production index | 15 Oct | Open-weight models carry most tokens, not most spend | | Claude Opus 5.5 fast mode | out of preview | Beta header now optional; use it where output speed matters | | Compliance API user preferences | beta, 15 Oct | Enterprise admins can now audit saved instructions | | Claude Code | 2.1.299 to 2.1.302 | Recheck headless runs and MCP allow rules | | Source control at Anthropic | 13 Oct | A read on agent-scale git load; nothing to install | ## Next.js and React ### React 19.0.9 to 19.3.1: a critical RCE in Server Components All four React lines got a patch on 14 October 2026, each listing one change under React Server Components, "Improve transport protocol" (releases [19.0.9](https://github.com/react/react/releases/tag/v19.0.9), [19.1.10](https://github.com/react/react/releases/tag/v19.1.10), [19.2.9](https://github.com/react/react/releases/tag/v19.2.9) and [19.3.1](https://github.com/react/react/releases/tag/v19.3.1)). The reason is in two advisories published the same day: an [unauthenticated remote code execution in React Server Components](https://github.com/react/react/security/advisories/GHSA-xqc2-xf4c-x3h3) (GHSA-xqc2-xf4c-x3h3), rated critical (CVSS 9.5), in `react-server-dom-webpack`, `-turbopack` and `-parcel` from 19.0.0 to 19.3.0, and a [denial of service in Server Functions](https://github.com/react/react/security/advisories/GHSA-h3gv-c5rc-p453) (GHSA-h3gv-c5rc-p453), rated high. The advisory says the RCE needs "extremely rare cases where responses transport multiple typed arrays and an attacker-controlled value", and still recommends updating immediately. Our take: rare preconditions are not a reason to wait when the fix is a patch release. If your React runs only in the browser you are not affected; anything with Server Components or Server Functions should move to the patch of its line today. ### Next.js 16.4.1 and 16.4.2: three advisories, then a patch [Next.js 16.4.1](https://github.com/vercel/next.js/releases/tag/v16.4.1) and [15.5.28](https://github.com/vercel/next.js/releases/tag/v15.5.28) were released on 14 October 2026 with fixes for three advisories; 15.5.28 carries the two that reach the 15.x line. GHSA-673q-mjm6-r5xr is a critical [RCE in `use cache` functions returning typed arrays](https://github.com/vercel/next.js/security/advisories/GHSA-673q-mjm6-r5xr), in apps using Cache Components with a `use cache` function that returns multiple typed arrays (16.0.0 to 16.4.0). GHSA-2464-fhr4-w9xw is a critical [RCE in the Image Optimization API with SVG files](https://github.com/vercel/next.js/security/advisories/GHSA-2464-fhr4-w9xw), through an upstream library, on glibc-based Linux (10.0.0 to 15.5.27 and 16.0.0 to 16.4.0); its workaround is making sure Next.js resolves `sharp` 0.35.5 or later. GHSA-p3m5-59mp-jv5r is a high-severity [denial of service in App Router apps using Server Actions](https://github.com/vercel/next.js/security/advisories/GHSA-p3m5-59mp-jv5r), any app with at least one, with no workaround besides upgrading. A day later, on 15 October, [Next.js 16.4.2](https://github.com/vercel/next.js/releases/tag/v16.4.2) followed with eight backported changes, mostly Turbopack and turbo-tasks fixes (garbage collection, lazy dynamic-import chunk collisions, realpath errors during resolution, snapshot consistency), plus a Pages Router dev fix and documentation. None of its entries is a security fix. Our take: go straight to 16.4.2, which carries 16.4.1's fixes, and check your lockfile for `sharp` while you are there. The `use cache` advisory recommends upgrading even if no function of yours returns typed arrays. ### Partial Prefetching in v0, with the Next.js 16.4 Skill On 16 October 2026 the Next.js team wrote up [how v0 improved its navigations with Next.js 16.4](https://nextjs.org/blog/improving-navigation-experience-in-v0-with-nextjs-16-4): an agent with the new `next-partial-prefetching-optimizer` Skill wrote an `instant()` Playwright test for each navigation, then refactored with `'use cache: remote'`, `'use cache: private'` and the new `navigation()` API until the test passed. The first rollout raised prefetch requests to `/templates/[id]` 2.9×, which they fixed by starting the richer prefetch of a card only on hover, focus or touch. After all the changes, total daily cost was 2.9% lower, with Runtime Cache spend at 4.3× its old level; as traffic changed over the same period, the team reads that as "not more expensive", not as savings. The post also notes that from 16.4, `create-next-app` turns on Cache Components and Partial Prefetching by default. Our take: the 2.9× jump is the part to remember. `prefetch={true}` on every card of a large grid costs requests, which matches what we saw in our own benchmark on pages with many links; prefetch on intent there, and keep the `instant()` test in CI. ## Vercel ### Python on Vercel is generally available [Python on Vercel became generally available](https://vercel.com/blog/python-on-vercel-is-now-generally-available) on 15 October 2026. It runs CPython on Linux on Fluid compute, detects FastAPI, Flask, Django and FastHTML, and reads dependency files, including those managed by `uv`. Vercel Services puts a Python backend and a frontend in one project, and `vercel dev` runs both locally. [Vercel Daemons](https://vercel.com/changelog/vercel-daemons-is-now-in-public-beta), for long-running workers such as queue consumers, entered public beta the same day. Our take: a FastAPI service beside a Next.js app no longer needs a second host, and the two share previews. Queue workers and anything that must stay up are still on a beta, so keep those where they run today. ### AI Gateway production index: open weight at 71.5% of tokens, 23% of spend Vercel's [AI Gateway production index for October 2026](https://vercel.com/blog/ai-gateway-production-index-october-2026), published on 15 October, reports that open-weight models processed 71.5% of gateway tokens in September and took 23% of spend, estimated at list prices. Anthropic's share of spend fell below half for the first time, to 43.9%, and the average price per token was 47% lower than in December. Our take: tokens and dollars tell different stories. The split suggests teams send bulk work to cheap open-weight models and keep paying for frontier models where quality decides; if all your traffic goes to one model, that split is worth testing. ## Claude ### Fast mode for Claude Opus 5.5 is out of research preview Since 15 October 2026, per the [Claude release notes](https://platform.claude.com/docs/en/release-notes/overview), [fast mode](https://platform.claude.com/docs/en/build-with-claude/fast-mode) for Claude Opus 5.5 needs neither an access request nor the `fast-mode-2026-02-01` beta header, and has a default rate limit in the Start, Build and Scale usage tiers. You set `speed: "fast"` on the request; it gives up to 2.5× more output tokens per second, not a faster first token, at $8 per million input tokens and $40 per million output tokens. Switching speeds misses the prompt cache, and fast mode doesn't work with the Batch API, a Priority Tier commitment or Claude Platform on AWS. Fast mode for Opus 5 and Opus 4.8 stays in research preview, with the header. The same day it came to Claude in Microsoft Foundry for deployments hosted on Azure. Our take: use it where a person watches the output stream, such as a coding agent or a chat reply, and keep a conversation on one speed so the cache holds. Read `usage.speed` in the response to see which speed served the request. ### The Compliance API returns members' saved instructions Also on 15 October, the [Compliance API](https://platform.claude.com/docs/en/manage-claude/compliance-api) began returning what each member saved as Instructions for Claude in claude.ai and as Global instructions in Cowork, in beta for Claude Enterprise: `GET /v1/compliance/organizations/{org_uuid}/user_preferences` with the `read:compliance_user_data` scope. Our take: saved instructions can hold client names and internal rules. Teams with an audit duty now have a way to see them, and members should know that admins can. ### Claude Code 2.1.299 to 2.1.302 Four releases came out between 14 and 16 October 2026: 2.1.299, [2.1.300](https://github.com/anthropics/claude-code/releases/tag/v2.1.300), [2.1.301](https://github.com/anthropics/claude-code/releases/tag/v2.1.301) and 2.1.302. [2.1.299](https://github.com/anthropics/claude-code/releases/tag/v2.1.299) added idle compaction (a conversation over 200K tokens left idle for about 54 minutes is compacted before its one-hour prompt cache expires; `"idleCompaction": false` turns it off) and made MCP allow rules match only the server they name, so `mcp__a` no longer allows a server called `a__b`. [2.1.302](https://github.com/anthropics/claude-code/releases/tag/v2.1.302) starts `claude -p` and Agent SDK sessions with no permission mode in `default` mode on third-party providers when telemetry is off or the install is fresh. On every provider, it also turns fork subagents on by default in `claude -p`, the Agent SDK, the desktop app and VS Code, as they already were in the terminal (`CLAUDE_CODE_FORK_SUBAGENT=0` turns them off). Our take: if you run Claude Code headless in CI, pin the version and pass `--permission-mode` explicitly, and if you wrote MCP allow rules with a short prefix, rewrite them as `mcp____*`. ### Redesigning source control at Anthropic On 13 October 2026 Anthropic described [why it replaced git for its monorepo](https://www.anthropic.com/engineering/redesigning-source-control) (updated 15 October): daily merges grew from about 2,500 in May 2026 to over 30,000 by September, with about 25 million CI checkouts a day. A team of seven built Scion, a version control system designed for always-online agents, and moved the monorepo in five months; Anthropic says Scion is "by no means a suitable replacement for git for general use". Our take: nothing to install, as Scion is internal. It is a measure of where agent-driven repositories go: if your agents open pull requests, expect merge and checkout volume, not developers, to set your CI's limits. ## Further reading - [React: Unauthenticated Remote Code Execution in React Server Components](https://github.com/react/react/security/advisories/GHSA-xqc2-xf4c-x3h3): The critical advisory of 14 October 2026, with the affected and patched versions. - [Next.js: Remote Code Execution in use cache functions](https://github.com/vercel/next.js/security/advisories/GHSA-673q-mjm6-r5xr): Who is affected on 16.0.0 to 16.4.0 and why to upgrade anyway. - [Claude: Fast mode](https://platform.claude.com/docs/en/build-with-claude/fast-mode): Supported models, pricing, rate limits and how to fall back to standard speed.