Netlify Release Notes

Google’s Gemini Nano Banana 2.1 is now available through Netlify AI Gateway. You can call this image generation model from Netlify Functions without configuring API keys; AI Gateway provides the connection to Google for you. Use the Google Gen AI SDK with the model ID gemini-nano-banana-2.1. Here’s an example that generates an image from a prompt and returns it directly from a Function: import { GoogleGenAI } from '@google/genai'; // Netlify Function: Generate an image with Gemini Nano Banana 2.1 and return it directly. // Usage (GET): /.netlify/functions/nano-banana-2-1?prompt=Your+prompt+here // Returns: binary image (PNG/JPEG/etc) with proper content-type. If no image, JSON error. export default async (request: Request) => { const url = new URL(request.url); const prompt = url.searchParams.get('prompt') || 'two happy bananas holding flashlights'; const ai = new GoogleGenAI({}); try { const response = await ai.models.generateContent({ model: 'gemini-nano-banana-2.1', contents: prompt, config: { imageConfig: { aspectRatio: '16:9', imageSize: '1K' } } }); let imagePart = null; for (const part of response.candidates[0].content.parts) { if (part.inlineData) { imagePart = part.inlineData; break; } } const bytes = Buffer.from(imagePart.data, 'base64'); const mimeType = imagePart.mimeType || 'image/png'; return new Response(bytes, { status: 200, headers: { 'Content-Type': mimeType, 'Cache-Control': 'no-store' } }); } catch (err) { return new Response(JSON.stringify({ error: Stri…

SvelteKit 3 is out today, and it just works on Netlify on day one. To upgrade, run: npx sv migrate sveltekit-3 The migration tool handles most of the mechanical changes for you, including moving your config and updating imports. You can also check out the official migration guide. What’s new Some highlights include:

• Vite 8 — SvelteKit 3 requires Vite 8, bringing faster builds powered by Rolldown.
• Config lives in vite.config.ts — SvelteKit configuration moves out of svelte.config.js and into your Vite config, so Vite plugins can read it right away.
• Explicit environment variables are stable — Declare the environment variables your app depends on in src/env.ts, and specify whether each one is public and whether it’s resolved at build time or when the app boots. You get validation and type safety out of the box.
• $lib is now #lib — The $lib alias is replaced by #lib, using Node’s subpath imports. Imports need to be unambiguous, so write #lib/foo.ts or #lib/foo/index.ts.
• Shallow routing is built into goto — Use goto() with shallow: true instead of pushState and replaceState.
• Consistent error handling — All errors, including ones you throw with error(...), now go through your handleError hook.
• New service worker modules — $service-worker is replaced by imports from $app/env, $app/paths, and $app/manifest, with better type checking in service workers.
• Tracing is stable — Tracing support has moved out of the experimental namespace. …

The Next.js team has disclosed seven security vulnerabilities in Next.js (one high, five medium, one low), patched on September 30, 2026 in 15.5.27 and 16.3.8. The issues span server-side request forgery (SSRF), cache poisoning, and information disclosure. Several of them do not affect apps hosted on Netlify. Here's what Netlify customers need to know. Summary Some of these vulnerabilities affect Next.js sites hosted on Netlify (details in Impact on Netlify), so if you run Next.js on Netlify, we strongly recommend upgrading next to 15.5.27 or 16.3.8 and redeploying. The OpenNext Netlify Next.js adapter must also be updated to @netlify/plugin-nextjs 5.16.1; it's auto-installed by default, so a redeploy picks it up (a manual upgrade is only needed if you pin the version). See What should I do? for full steps. Vulnerabilities All issues are patched in 15.5.27 and 16.3.8. Vulnerability: GHSA-cjq9-62q9-8jv4 / CVE-2026-94483 — Image optimizer SSRF Severity: High Affected: 16.x with an attacker-controlled remote host in images.remotePatterns Vulnerability: GHSA-4jqv-mc3x-m676 / CVE-2026-94543 — Cache poisoning of SSG/ISR pages (cross-route) Severity: Medium Affected: 15.x/16.x Pages Router apps with SSG/ISR and a root catch-all route Vulnerability: GHSA-mcj8-r9mp-w47p / CVE-2026-94484 — Cache poisoning via encoded paths / /index (SSG/ISR) Severity: Medium Affected: 15.x/16.x apps combining a root catch-all with SSG/ISR routes Vulnerability: GHSA-f87g-xv8r-7p7x / CVE-2026-94485 — Met…

The TanStack team has disclosed a critical cross-site scripting (XSS) vulnerability in TanStack Start. A crafted URL can cause an affected app to return attacker-controlled HTML from its own origin, which may run attacker-supplied JavaScript in a visitor's browser. Here's what Netlify customers need to know. Vulnerabilities GHSA-qx66-fv34-fjm8 (CVE-2026-102989): Unauthenticated reflected XSS in server-function responses. Package: @tanstack/react-start Affected versions: >= 1.143.12, < 1.168.60 Fixed in: 1.168.60 Package: @tanstack/solid-start Affected versions: >= 1.143.12, < 1.168.57 Fixed in: 1.168.57 Package: @tanstack/vue-start Affected versions: >= 1.143.12, < 1.168.56 Fixed in: 1.168.56 Package: @tanstack/start-server-core Affected versions: >= 1.143.12, < 1.169.39 Fixed in: 1.169.39 Impact on Netlify This is a client-side cross-site scripting (XSS) vulnerability in TanStack Start's server-function response handling. Because the malicious response is returned from the app's own origin, an attacker who gets a victim to open a crafted link can run JavaScript in that visitor's session — for example, to read their data or act as them on the site. All applications on an affected version should upgrade. What should I do? We strongly recommend upgrading as soon as possible to the patched releases:

• @tanstack/react-start 1.168.60 or later
• @tanstack/solid-start 1.168.57 or later
• @tanstack/vue-start 1.168.56 or later
• @tanstack/start-server-core 1.169.39 or later …

Netlify's security and compliance document library has moved into the Netlify Dashboard. To request access and learn more about the certifications and documents available, go to https://www.netlify.com/trust-center/. Any signed-in user, on any plan, can view our certifications, subprocessor list, and available compliance documents from their user settings. More sensitive documents, such as our SOC 2 report, require an access request through the Trust Center in the Netlify dashboard. Once approved, the documents are available for download. Learn more about how to access the Netlify Trust Center in our Security docs.

OpenAI’s GPT-6.1 Sol model is 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. AI Gateway handles everything automatically. Here’s an example using GPT-6.1 Sol with the Responses API: import OpenAI from 'openai'; export default async () => { const openai = new OpenAI(); const response = await openai.responses.create({ model: 'gpt-6.1-sol', input: 'Give a concise explanation of how AI works.', }); return Response.json(response); }; GPT-6.1 Sol is also available across Scheduled Functions, Background Functions, and Edge Functions. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure. Learn more in the AI Gateway documentation and Agent Runners documentation.

Agent Runners now shows you a preview right next to your prompt. Previously, you’d get a link to the Deploy Preview and have to open it in a separate tab to see what the agent changed. Now the preview appears inline, so you can review the result and write your next prompt without switching back and forth. Plus, you can still access the Deploy Preview link if you need it. This makes iterating with an agent feel more like a conversation. See what changed, spot what’s off, and follow up with the next instruction, all in one view. Example flow For example, say you’re building a strategic task organizer and prompt your agent to add a button that generates a quarterly impact report. Now you can watch your agent’s updates in the side preview next to your prompt. Agent Runners side-by-side view showing a chat prompt to add a quarterly report button next to the live Deploy Preview of the resulting task organizer app In this example, your agent on Netlify will also let you know if your project cannot save your tasks across browser sessions yet, and you can approve adding a database in the same view. This is just one example of how Netlify gives you professional-grade capabilities, such as a real working database, with your agent of choice when you prompt with Agent Runners. Try it out See it in action when you start a new agent run or learn more about working with agents on Netlify.

Anthropic’s Claude Sonnet 5.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. AI Gateway handles everything automatically. Here’s an example using Claude Sonnet 5.5: import Anthropic from '@anthropic-ai/sdk'; export default async () => { const anthropic = new Anthropic(); const response = await anthropic.messages.create({ model: 'claude-sonnet-5-5', max_tokens: 4096, messages: [ { role: 'user', content: 'How can AI improve my coding?' } ] }); return Response.json(response); }; Claude Sonnet 5.5 is also available across Background Functions, Scheduled Functions, and Edge Functions. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure. Learn more in the AI Gateway documentation and Agent Runners documentation.

As part of our ongoing work to simplify the Netlify dashboard, we’ve added an activity feed to the project overview page. It’s available on all plans and adapts to how your project is set up. Now when you open a project, the activity feed gives you a snapshot of your project's latest updates, with quick access to:

• Production versions of your project, including the version last published
• Preview versions of your project
• Agent runs, so you can see what agents are working on and what you and your teammates have prompted

Project activity feed in the Netlify dashboard listing recent activity newest first, with filters for All, Production, Previews, and Agent runs. Entries include an in-progress agent run, a published production deploy, and two branch deploys with Preview links. This means that instead of tracking down Production deploy links, Deploy Preview links, branch deploy links, and your agent runs list separately, you can now see where your project stands at a glance in one single spot. The feed also suggests next steps to help you get started. It's one of several dashboard improvements we're gradually rolling out to simplify the Netlify experience, so you may have spotted a few already, with more to come.

The Next.js team has disclosed a critical severity vulnerability in an upstream dependency that can lead to remote code execution when ImageResponse renders untrusted input. It is patched in 15.5.26 and 16.3.6. Applications that do not pass untrusted input into ImageResponse are not expected to be affected. Here’s what Netlify customers need to know. Vulnerabilities

• GHSA-vcvr-r3jv-pc5j / CVE-2026-94545 — Remote Code Execution in next/og ImageResponse. Critical. Patched in 15.5.26 and 16.3.6.

Impact on Netlify Netlify sites are affected only if they use ImageResponse and the image it generates includes untrusted input — text, or an image loaded from the request. Sites that don’t use ImageResponse, or that only render trusted content through it, are not affected. For sites that do, the impact is limited to a crashed function invocation, not code execution. On Netlify, this has minimal impact: our autoscaling serverless architecture means that a malicious request resulting in a crashed function does not affect other requests. However, active exploitation could increase your function costs. What should I do? We strongly recommend upgrading as soon as possible to patched releases:

• next 15.5.26 or later, or 16.3.6 or later, then redeploy. …

Anthropic’s Claude Opus 5.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. AI Gateway handles everything automatically. Here’s an example using Claude Opus 5.5: import Anthropic from '@anthropic-ai/sdk'; export default async () => { const anthropic = new Anthropic(); const response = await anthropic.messages.create({ model: 'claude-opus-5-5', max_tokens: 4096, output_config: { effort: 'medium' }, messages: [ { role: 'user', content: 'How can AI improve my coding?', }, ], }); return new Response(JSON.stringify(response), { headers: { 'Content-Type': 'application/json' }, }); }; Claude Opus 5.5 is also available across Background Functions, Scheduled Functions, and Edge Functions. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure. Learn more in the AI Gateway documentation and Agent Runners documentation.

OpenAI’s GPT-6 Sol and GPT-6 Luna 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. AI Gateway handles everything automatically. Here’s an example using GPT-6 Sol with the Responses API: import OpenAI from 'openai'; export default async () => { const openai = new OpenAI(); const response = await openai.responses.create({ model: 'gpt-6-sol', input: 'Give a concise explanation of how AI works.', }); return Response.json(response); }; GPT-6 Sol and GPT-6 Luna are also available across Scheduled Functions, Background Functions, and Edge Functions. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure. Learn more in the AI Gateway documentation and Agent Runners documentation.

TypeSafe’s Jev model is now available through Netlify’s AI Gateway with zero configuration required. Install @typesafe-ai/sdk and use it directly in your Netlify Functions — no API keys to create, no provider config, no base URLs to wire up. AI Gateway handles credentials automatically, and usage is billed to your Netlify credits like every other model in the gateway. Jev is TypeSafe’s first “System One” model, and it works differently from the chat models you’re used to. Instead of generating prose, you send it your program state along with a set of typed questions, and it returns typed answers with calibrated probabilities. There are three question primitives: choice picks one option from a set, score rates against ordered levels, and noul returns a yes/no probability between 0 and 1. Answers are constrained to the options you declare, so there’s no JSON parsing or schema coercion on your end. Every question in a request is evaluated in parallel against the same state, which means batching a dozen questions into one call costs little more than asking one. State and questions share a budget of roughly 32,000 tokens — about 150,000 characters of English text — and TypeSafe reports end-to-end response times of 70–500ms, making Jev a good fit for classification, routing, extraction, scoring, and guardrail checks on the request path. The SDK defaults to the jev-latest alias, currently jev-1.13.0, and requires Node.js 20 or newer. Here’s a Function that routes an incoming contact…

DeepSeek V4.1 Flash is now available through OpenRouter on Netlify’s AI Gateway with zero configuration required. Use the OpenRouter SDK directly in your Netlify Functions without managing API keys or authentication. AI Gateway handles everything automatically. Here’s an example using DeepSeek V4.1 Flash: import { OpenRouter } from '@openrouter/sdk'; export default async () => { const client = new OpenRouter(); const response = await client.chat.send({ chatRequest: { model: 'deepseek/deepseek-v4.1-flash', messages: [{ role: 'user', content: 'How can AI improve my coding?' }], maxTokens: 400, }, }); return Response.json(response); }; DeepSeek V4.1 Flash is available across Background Functions, Scheduled Functions, and Edge Functions. You get automatic access to Netlify’s rate limiting and authentication infrastructure. Learn more in the AI Gateway documentation and OpenRouter documentation.

Agent Runners are now better at completing their work when a run has less credits remaining than the task requires. If you are close to running our of credits during a run, the agent will start focusing on delivering the most useful result it can with the credits it has left. It finishes work already in progress, leaves the project in a working state, and provides a clear summary of what it completed. Previously, an ambitious task could end abruptly before the agent wrapped up, leaving partial changes and little explanation. Now, you’re more likely to get a working result you can use right away, or a solid, clearly documented starting point for your next run. This improvement applies automatically to every agent and model available in Agent Runners. There’s nothing to enable or configure. Learn more in Make changes with Agent Runners and how credits work.

You can now connect repositories hosted on Cursor Origin to Netlify, so every Git push deploys an updated version of your project at a preview URL or a production URL. Netlify supports Cursor Origin with continuous deployment, meaning that once your codebase’s repo is connected, Netlify will automatically:

• Build and deploy your project with every git push
• Build Deploy Previews for your pull requests
• Send deploy notifications to your pull request comments on Cursor Origin so you can check preview URLs there

Requirements Cursor Origin uses OAuth authentication, so connecting a repo works much like our existing Azure DevOps support: the Cursor user who authenticates needs access to the Cursor Origin codebase that owns the repository. To use Cursor Origin with Netlify, you do not need a specific pricing plan with Netlify. Support scope Note that features outside of continuous deployment, such as Agent Runners and the Netlify Drawer, are not supported at this time. Get started To learn more, check out these docs:

• Get started Cursor Origin
• Link your repo to your Netlify project
• Deploy a new project to Netlify from your Cursor Origin repo

OpenAI’s ChatGPT Images 2.5 models are now available through Netlify’s AI Gateway and Agent Runners with zero configuration required. Use gpt-image-2.5-flare or gpt-image-2.5-sunburst to generate images for your applications. Use the OpenAI SDK directly in your Netlify Functions without managing API keys or authentication. AI Gateway handles everything automatically. Here’s an example using the gpt-image-2.5-flare model: import OpenAI from 'openai'; const ai = new OpenAI(); export default async (req, context) => { const response = await ai.images.generate({ model: 'gpt-image-2.5-flare', prompt: 'A golden retriever working at a laptop in a sunny startup office', size: '1024x1024', quality: 'low', output_format: 'jpeg', output_compression: 80 }); const imageBuffer = Buffer.from(response.data[0].b64_json, 'base64'); return new Response(imageBuffer, { status: 200, headers: { 'content-type': 'image/jpeg', 'cache-control': 'no-store' } }); }; Both ChatGPT Images 2.5 models are available across standard Functions, Background Functions, Scheduled Functions, Edge Functions, and Agent Runners. You get automatic access to Netlify’s caching, rate limiting, and authentication infrastructure. Learn more in the AI Gateway documentation and Agent Runners documentation.