--- title: "Changelog | Netlify" description: "Stay updated with the latest features, fixes, and improvements. Realize the speed, agility and performance of a scalable, composable web architecture with Netlify. Explore the composable web platform now!" source: "https://www.netlify.com/changelog/page/3/" last_updated: "2026-08-27T21:43:47.000Z" --- # Changelog All Tags Agent-runners AI Ai-gateway Angular Astro AX Build CLI Database Design Devtools Domains E-commerce Extensions Forms Framework Functions Logs Next.js Nuxt.js Remix SDK Security Updates Workflow [Subscribe to feed](https://www.netlify.com/changelog/feed.xml) - [ ## Security Update: Multiple vulnerabilities in Next.js ](/changelog/2026-07-21-nextjs-security-vulnerabilities/) July 21, 2026 - [security](/changelog/tag/security/) - [next.js](/changelog/tag/next-js/) The Next.js team has disclosed [nine security vulnerabilities](https://github.com/vercel/next.js/security), all patched in **15.5.21** and **16.2.11**. The issues span server-side request forgery (SSRF), a middleware authorization bypass, denial of service (DoS), and cache/identifier disclosure. Here’s what Netlify customers need to know. ## Summary If you run Next.js on Netlify, **upgrade `next` to 15.5.21 or 16.2.11** and redeploy. Netlify-hosted sites are **not affected** by three of these (Server Action `Host` forwarding, the Image Optimizer DoS, and the Edge-runtime OOM). The rest affect only apps using a specific pattern or configuration, and are resolved by upgrading — see [Impact on Netlify](#impact-on-netlify) for the per-issue verdict. ## Vulnerabilities All issues are patched in **15.5.21** and **16.2.11**. Earlier minors of 15.x and 16.x will not be patched; affected projects must upgrade to a patched minor. Follow the GHSA links for full details. Vulnerability Severity Affected versions [CVE-2026-64645](https://www.cve.org/CVERecord?id=CVE-2026-64645) / [GHSA-p9j2-gv94-2wf4](https://github.com/vercel/next.js/security/advisories/GHSA-p9j2-gv94-2wf4) — Server-Side Request Forgery in rewrites via attacker-controlled destination hostname High ≥12.0.0 <15.5.21, ≥16.0.0 <16.2.11 [CVE-2026-64649](https://www.cve.org/CVERecord?id=CVE-2026-64649) / [GHSA-89xv-2m56-2m9x](https://github.com/vercel/next.js/security/advisories/GHSA-89xv-2m56-2m9x) — Server-Side Request Forgery in Server Actions on custom servers High ≥14.1.1 <15.5.21, ≥16.0.0 <16.2.11 [CVE-2026-64642](https://www.cve.org/CVERecord?id=CVE-2026-64642) / [GHSA-6gpp-xcg3-4w24](https://github.com/vercel/next.js/security/advisories/GHSA-6gpp-xcg3-4w24) — Middleware / Proxy bypass in App Router applications using Turbopack and single locale High ≥16.0.0 <16.2.11 [CVE-2026-64641](https://www.cve.org/CVERecord?id=CVE-2026-64641) / [GHSA-m99w-x7hq-7vfj](https://github.com/vercel/next.js/security/advisories/GHSA-m99w-x7hq-7vfj) — Denial of Service in App Router using Server Actions High ≥13.0.0 <15.5.21, ≥16.0.0 <16.2.11 [CVE-2026-64644](https://www.cve.org/CVERecord?id=CVE-2026-64644) / [GHSA-q8wf-6r8g-63ch](https://github.com/vercel/next.js/security/advisories/GHSA-q8wf-6r8g-63ch) — Denial of Service in the Image Optimization API using SVGs Medium ≥15.5.0 <15.5.21, ≥16.0.0 <16.2.11 [CVE-2026-64646](https://www.cve.org/CVERecord?id=CVE-2026-64646) / [GHSA-4c39-4ccg-62r3](https://github.com/vercel/next.js/security/advisories/GHSA-4c39-4ccg-62r3) — Unbounded Server Action payload in Edge runtime Medium ≥13.0.0 <15.5.21, ≥16.0.0 <16.2.11 [CVE-2026-64648](https://www.cve.org/CVERecord?id=CVE-2026-64648) / [GHSA-68g3-v927-f742](https://github.com/vercel/next.js/security/advisories/GHSA-68g3-v927-f742) — Cache confusion of response bodies for requests with bodies Medium ≥13.0.0 <15.5.21, ≥16.0.0 <16.2.11 [CVE-2026-64647](https://www.cve.org/CVERecord?id=CVE-2026-64647) / [GHSA-4633-3j49-mh5q](https://github.com/vercel/next.js/security/advisories/GHSA-4633-3j49-mh5q) — Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences Medium ≥13.0.0 <15.5.21, ≥16.0.0 <16.2.11 [CVE-2026-64643](https://www.cve.org/CVERecord?id=CVE-2026-64643) / [GHSA-955p-x3mx-jcvp](https://github.com/vercel/next.js/security/advisories/GHSA-955p-x3mx-jcvp) — Unauthenticated disclosure of internal Server Function endpoints Medium ≥13.0.0 <15.5.21, ≥16.0.0 <16.2.11 ## Impact on Netlify ### Server-side request forgery [CVE-2026-64645](https://www.cve.org/CVERecord?id=CVE-2026-64645) / [GHSA-p9j2-gv94-2wf4](https://github.com/vercel/next.js/security/advisories/GHSA-p9j2-gv94-2wf4) (Server-Side Request Forgery in rewrites via attacker-controlled destination hostname): Netlify sites are **affected** if a `rewrites()` or `redirects()` rule builds the destination hostname from request input (static destinations are not). Upgrading Next.js resolves it. [CVE-2026-64649](https://www.cve.org/CVERecord?id=CVE-2026-64649) / [GHSA-89xv-2m56-2m9x](https://github.com/vercel/next.js/security/advisories/GHSA-89xv-2m56-2m9x) (Server-Side Request Forgery in Server Actions on custom servers): Netlify sites are **not affected** — our edge overwrites inbound `X-Forwarded-Host` with the real host, so an attacker cannot redirect the Server Action’s outbound request to a host they control. ### Middleware authorization bypass [CVE-2026-64642](https://www.cve.org/CVERecord?id=CVE-2026-64642) / [GHSA-6gpp-xcg3-4w24](https://github.com/vercel/next.js/security/advisories/GHSA-6gpp-xcg3-4w24) (Middleware / Proxy bypass in App Router applications using Turbopack and single locale): Netlify sites are **affected** if they build with Turbopack and use the legacy `middleware.ts` convention with single-locale i18n. Webpack builds and the newer `proxy.ts` convention are not affected. Upgrading Next.js resolves it. ### Denial of service [CVE-2026-64641](https://www.cve.org/CVERecord?id=CVE-2026-64641) / [GHSA-m99w-x7hq-7vfj](https://github.com/vercel/next.js/security/advisories/GHSA-m99w-x7hq-7vfj) (Denial of Service in App Router using Server Actions) and [CVE-2026-64646](https://www.cve.org/CVERecord?id=CVE-2026-64646) / [GHSA-4c39-4ccg-62r3](https://github.com/vercel/next.js/security/advisories/GHSA-4c39-4ccg-62r3) (Unbounded Server Action payload in Edge runtime) are server-side DoS. On Netlify these have **minimal impact**: our autoscaling architecture means a hung or crashed function does not affect other requests, though active exploitation could increase your function costs. The Edge-runtime OOM specifically **cannot exhaust memory on Netlify** — request bodies are capped and each request runs in an isolated invocation. Upgrading Next.js resolves both. [CVE-2026-64644](https://www.cve.org/CVERecord?id=CVE-2026-64644) / [GHSA-q8wf-6r8g-63ch](https://github.com/vercel/next.js/security/advisories/GHSA-q8wf-6r8g-63ch) (Denial of Service in the Image Optimization API using SVGs): Netlify sites are **not affected** — `/_next/image` is served by [Netlify Image CDN](https://docs.netlify.com/build/image-cdn/overview/), so the vulnerable Next.js code path is not used. ### Cache disclosure / confusion [CVE-2026-64648](https://www.cve.org/CVERecord?id=CVE-2026-64648) / [GHSA-68g3-v927-f742](https://github.com/vercel/next.js/security/advisories/GHSA-68g3-v927-f742) (Cache confusion of response bodies for requests with bodies) and [CVE-2026-64647](https://www.cve.org/CVERecord?id=CVE-2026-64647) / [GHSA-4633-3j49-mh5q](https://github.com/vercel/next.js/security/advisories/GHSA-4633-3j49-mh5q) (Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences): Netlify sites are **affected** if they use the specific cached-fetch patterns — a cached `fetch(new Request(url), init)`, or a cached binary-body POST `fetch()`. `fetch(url, init)` and `cache: 'no-store'` are not affected. Upgrading Next.js resolves both. ### Information disclosure [CVE-2026-64643](https://www.cve.org/CVERecord?id=CVE-2026-64643) / [GHSA-955p-x3mx-jcvp](https://github.com/vercel/next.js/security/advisories/GHSA-955p-x3mx-jcvp) (Unauthenticated disclosure of internal Server Function endpoints): Netlify sites are **affected** (low impact) if they use Cache Components with a reflective Server Action co-bundled alongside a `use cache` function. The leak is limited to opaque internal function identifiers — no credentials or PII. Upgrading Next.js resolves it. ## What should I do? We strongly recommend upgrading as soon as possible: - Upgrade `next` to **15.5.21** or **16.2.11**, then redeploy. For Next.js 13.x and 14.x: patches target 15.x / 16.x — upgrade to a patched minor. Note that any publicly available deploy previews and branch deploys may remain vulnerable until they are [automatically deleted](https://docs.netlify.com/deploy/manage-deploys/manage-deploys-overview/#automatic-deploy-deletion). Consider [deleting these deploys manually](https://docs.netlify.com/deploy/manage-deploys/manage-deploys-overview/#manual-deploy-deletion-through-the-netlify-ui). ## Resources - [Next.js July 2026 security release](https://nextjs.org/blog/july-2026-security-release) - [Next.js security advisories](https://github.com/vercel/next.js/security) [Permalink to Security Update: Multiple vulnerabilities in Next.js Permalink](/changelog/2026-07-21-nextjs-security-vulnerabilities/) - [ ## Google Gemini 3.6 Flash and Gemini 3.5 Flash-Lite Now Available in AI Gateway and Agent Runners ](/changelog/gemini-3-6-flash-3-5-flash-lite-ai-gateway-agent-runners/) July 21, 2026 - [ai gateway](/changelog/tag/ai-gateway/) - [agent runners](/changelog/tag/agent-runners/) Google’s Gemini 3.6 Flash and Gemini 3.5 Flash-Lite models are now available through Netlify’s AI Gateway and Agent Runners with zero configuration required. Use the Google GenAI SDK directly in your Netlify Functions without managing API keys or authentication. The AI Gateway handles everything automatically. Here’s an example using the Gemini 3.6 Flash model: ``` import { GoogleGenAI } from '@google/genai'; export default async () => { const ai = new GoogleGenAI({}); const response = await ai.models.generateContent({ model: 'gemini-3.6-flash', contents: 'How can AI improve my coding?', }); return Response.json(response);}; ``` Gemini 3.6 Flash and Gemini 3.5 Flash-Lite are available for all Function types and Agent Runners. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure. Learn more in the [AI Gateway documentation](https://docs.netlify.com/build/ai-gateway/overview/) and [Agent Runners documentation](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/). [Permalink to Google Gemini 3.6 Flash and Gemini 3.5 Flash-Lite Now Available in AI Gateway and Agent Runners Permalink](/changelog/gemini-3-6-flash-3-5-flash-lite-ai-gateway-agent-runners/) - [ ## Invite Developers and Internal Builders without assigning a project ](/changelog/2026-07-20-invite-builders-without-project-access/) July 20, 2026 - [workflow](/changelog/tag/workflow/) You can now invite a [Developer](https://docs.netlify.com/manage/accounts-and-billing/team-management/roles-and-permissions/#developer) or [Internal Builder](https://docs.netlify.com/manage/accounts-and-billing/team-management/roles-and-permissions/#internal-builder) to your team without assigning them to an existing project. Previously, the UI required every new Developer or Internal Builder to be given access to at least one existing project before you could add them. That got in the way of a common workflow: bringing someone on specifically to spin up new work, without handing them the keys to projects they don’t need to touch. Because both roles can create their own projects directly, this is often exactly what teams want. Invite a new teammate, let them start building right away, and keep your existing projects untouched. When they create a project, they’re automatically assigned the Developer role on it, so they own the work they start without gaining access to everything else. The result is cleaner, least-privilege onboarding: people get exactly the access they need to begin, and nothing more. To try it, head to your team’s Members page and invite a Developer or Internal Builder without selecting any existing projects. Learn more about managing project access in our [project access docs](https://docs.netlify.com/manage/accounts-and-billing/team-management/manage-project-access). [Permalink to Invite Developers and Internal Builders without assigning a project Permalink](/changelog/2026-07-20-invite-builders-without-project-access/) - [ ## Set AI usage limits for individual team members ](/changelog/2026-07-15-per-member-ai-usage-limits/) July 15, 2026 - [agent runners](/changelog/tag/agent-runners/) Team Owners on [Pro plans](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/) can now limit [Agent Runners](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/) spend for individual members in your team, giving you finer control over how AI credits are used across your team. Set a single credit limit that applies to every member, then customize it with overrides for specific people who need more (or less) room to work. This makes it easy to give power users a higher ceiling while keeping predictable, budget-friendly defaults for everyone else. You’ll find these controls in **Team Settings** under **General > AI Enablement**. This builds on our existing [team-wide AI usage limits](https://docs.netlify.com/build/build-with-ai/manage-ai-features/#limit-ai-feature-usage), so you can now manage AI spend both for an entire team and down to each individual member. We’ve also updated how AI inference credit usage is displayed in your dashboard, making it easier to monitor AI usage and manage your AI spend. Learn more about [AI inference usage](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/how-credits-work/#credit-usage-for-ai-inference) and [how credits work](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/how-credits-work/). [Permalink to Set AI usage limits for individual team members Permalink](/changelog/2026-07-15-per-member-ai-usage-limits/) - [ ## Introducing Pro plan monthly credit tiers with rollovers ](/changelog/2026-07-14-pro-plan-credit-tiers/) July 14, 2026 - [workflow](/changelog/tag/workflow/) Team Owners on the credit-based Pro plan can now choose how many monthly credits come with their plan, instead of a single fixed amount. Pick the tier that fits your usage, and change it whenever your needs shift. The new credit tiers, with rollover on higher tiers, can be especially helpful for teams with seasonal surges and teams with consistently high-credit usage and come with some per-credit cost savings. ## What’s changing Previously, every Pro plan included a fixed 3,000 monthly credits for $20/month. ### New amounts for monthly credits Now you can choose from five tiers: Monthly credits Price Rollover 3,000 $20/mo No 5,000 $33/mo Yes 10,000 $63/mo Yes 15,000 $95/mo Yes 20,000 $126/mo Yes All tiers include the same Pro plan features: unlimited seats, password protection, and everything else that comes with Pro. ### Rollover credits on higher tiers Choose 5,000 monthly credits or higher and unused credits rollover an additional billing cycle so you get an extra month to use them. The base 3,000-credit tier doesn’t roll over. ### Change your tier anytime Team Owners can switch tiers without limits to how many times they switch. Upgrades take effect immediately with a prorated refund; downgrades take effect next billing cycle. Learn more about [switching between Pro tiers](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/#pro-plan). ## Learn more - [Pro plan](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/) - [How credits work](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/how-credits-work/) - [Change your pricing plan](https://docs.netlify.com/manage/accounts-and-billing/billing/change-your-pricing-plan/#change-your-pro-plan-credit-allotment) - [Buy credit packs](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/buy-credit-packs/) [Permalink to Introducing Pro plan monthly credit tiers with rollovers Permalink](/changelog/2026-07-14-pro-plan-credit-tiers/) - [ ## OpenAI GPT-5.6 Sol, Luna, and Terra Now Available in AI Gateway and Agent Runners ](/changelog/gpt-5-6-sol-luna-terra-ai-gateway-agent-runners/) July 9, 2026 - [ai gateway](/changelog/tag/ai-gateway/) - [agent runners](/changelog/tag/agent-runners/) OpenAI’s GPT-5.6 Sol, Luna, and Terra models are now available through Netlify’s AI Gateway and Agent Runners with zero configuration required. Use the OpenAI SDK directly in your Netlify Functions without managing API keys or authentication. The AI Gateway handles everything automatically. Here’s an example using the GPT-5.6 Sol model: ``` import OpenAI from 'openai'; export default async () => { const openai = new OpenAI(); const response = await openai.responses.create({ model: 'gpt-5.6-sol', input: 'Give a concise explanation of how AI works.', }); return Response.json(response);}; ``` GPT-5.6 Sol, Luna, and Terra are available for all Function types and Agent Runners. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure. Learn more in the [AI Gateway documentation](https://docs.netlify.com/build/ai-gateway/overview/) and [Agent Runners documentation](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/). [Permalink to OpenAI GPT-5.6 Sol, Luna, and Terra Now Available in AI Gateway and Agent Runners Permalink](/changelog/gpt-5-6-sol-luna-terra-ai-gateway-agent-runners/) - [ ## Node.js 24 is now the default for Builds and Functions on new sites ](/changelog/2026-07-07-nodejs-24-default-new-sites/) July 7, 2026 - [build](/changelog/tag/build/) - [functions](/changelog/tag/functions/) New sites created on Netlify now use Node.js 24 by default for both builds and Netlify Functions. Existing sites aren’t affected — they keep using whatever Node.js version they’re currently pinned to, whether that’s set via a `NODE_VERSION` environment variable, an `.nvmrc`/`.node-version` file, or the `engines.node` field in `package.json`. If you want to move an existing site to Node.js 24, follow the [Node.js version configuration guide](https://docs.netlify.com/build/configure-builds/manage-dependencies/#node-js-and-javascript) for builds, and the [functions runtime version guide](https://docs.netlify.com/build/functions/optional-configuration/?fn-language=js&data-tab=TypeScript#nodejs-version-for-runtime) for Netlify Functions. [Permalink to Node.js 24 is now the default for Builds and Functions on new sites Permalink](/changelog/2026-07-07-nodejs-24-default-new-sites/) - [ ## Claude Fable 5 reactivated in AI Gateway ](/changelog/claude-fable-5-re-enabled/) July 1, 2026 - [ai gateway](/changelog/tag/ai-gateway/) Anthropic’s Claude Fable 5 model is once again available through Netlify’s AI Gateway with zero configuration required. Use the Anthropic SDK directly in your Netlify Functions without managing API keys or authentication. The AI Gateway handles everything automatically. Here’s an example using the Claude Fable 5 model: ``` import Anthropic from '@anthropic-ai/sdk'; export default async () => { const anthropic = new Anthropic(); const response = await anthropic.messages.create({ model: 'claude-fable-5', max_tokens: 4096, messages: [ { role: 'user', content: 'How can AI improve my coding?' } ] }); return new Response(JSON.stringify(response), { headers: { 'Content-Type': 'application/json' } });}; ``` Claude Fable 5 is available for all Function types. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure. Learn more in the [AI Gateway documentation](https://docs.netlify.com/build/ai-gateway/overview/). [Permalink to Claude Fable 5 reactivated in AI Gateway Permalink](/changelog/claude-fable-5-re-enabled/) - [ ## Claude Sonnet 5 now available in AI Gateway and Agent Runners ](/changelog/claude-sonnet-5-ai-gateway-agent-runners/) June 30, 2026 - [ai gateway](/changelog/tag/ai-gateway/) - [agent runners](/changelog/tag/agent-runners/) Anthropic’s Claude Sonnet 5 model is now available through Netlify’s AI Gateway and Agent Runners with zero configuration required. Use the Anthropic SDK directly in your Netlify Functions without managing API keys or authentication. The AI Gateway handles everything automatically. Here’s an example using the Claude Sonnet 5 model: ``` import Anthropic from '@anthropic-ai/sdk'; export default async () => { const anthropic = new Anthropic(); const response = await anthropic.messages.create({ model: 'claude-sonnet-5', max_tokens: 4096, messages: [ { role: 'user', content: 'How can AI improve my coding?' } ] }); return Response.json(response);}; ``` Claude Sonnet 5 is available for all Function types and Agent Runners. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure. Learn more in the [AI Gateway documentation](https://docs.netlify.com/build/ai-gateway/overview/) and [Agent Runners documentation](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/). [Permalink to Claude Sonnet 5 now available in AI Gateway and Agent Runners Permalink](/changelog/claude-sonnet-5-ai-gateway-agent-runners/) [Previous page](/changelog/page/2) [Next page](/changelog/page/4)