Changelog

Enterprise teams can now create, track, and reply to support tickets without leaving Netlify in our new Support Hub. Go to User settings > Support to see your tickets, check their status, and continue your conversation with the Netlify support team.

Team Owners can see every ticket their team members created, not just their own. The Requester column shows who opened each ticket. Members on your team can only view the tickets they opened.

What you can do

• Create tickets with a subject, a Markdown description, and CC recipients.
• Track progress with clear statuses: Open, Awaiting customer response, and Closed.
• Search, sort, and filter your tickets, including tickets you’re CC’d on.
• Reply from the dashboard. Your reply goes straight to the support team.

Not on Enterprise?

Support is available on every plan, including Free plans. Use the Netlify Support page or email support@netlify.com.

Learn more

Learn more from our Support Hub guide

TypeSafe’s Jev 1.14.0 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 without managing API keys or authentication. AI Gateway handles credentials automatically, and usage is billed to your Netlify credits.

Jev answers typed questions about your application state. Here’s an example using jev-1.14.0 to categorize a support ticket as a bug, feature request, or question:

import { choice, TypeSafeClient } from '@typesafe-ai/sdk';

export default async () => {
    const typesafe = new TypeSafeClient();

    const response = await typesafe.systemOne({
        model: 'jev-1.14.0',
        state: { issue: 'App crashes when I click Save.' },
        questions: {
            label: choice('Categorize this ticket', {
                bug: null,
                feature: null,
                question: null,
            }),
        },
    });

    return Response.json(response);
};

Jev 1.14.0 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 the TypeSafe documentation.

The Next.js and React teams have disclosed three security vulnerabilities (two critical, one high), released on October 14, 2026: a remote code execution (RCE) in SVG image processing, an RCE in use cache (Cache Components), and a denial of service (DoS) in App Router Server Actions. Here’s what Netlify customers need to know.

Summary

If you run Next.js on Netlify, we strongly recommend upgrading next to 15.5.28 or 16.4.1 and redeploying. Several of these have limited or no impact on Netlify; see Impact on Netlify. See What should I do? for steps.

Vulnerabilities

All issues are patched in 15.5.28 and 16.4.1.

Impact on Netlify

Remote code execution

GHSA-673q-mjm6-r5xr is a Critical RCE affecting Next.js 16.x apps using Cache Components, triggered by a use cache function that returns typed arrays — an unusual configuration not expected in normally functioning applications. On Netlify, apps that meet those conditions are affected; upgrading Next.js resolves it.

GHSA-2464-fhr4-w9xw (CVE-2026-96889) is an RCE in the image library (sharp) Next.js uses to process SVGs. The advisory describes it through the next/image Image Optimization API — which on Netlify is served by Netlify Image CDN, not your function, so that path is not exercised on Netlify. The same flaw is reachable through next/og ImageResponse, which does run in your Netlify function: apps that render untrusted input via ImageResponse are affected. There, the impact is limited to a crashed function invocation, not code execution — minimal impact on our autoscaling serverless architecture, though active exploitation could increase your function costs. Upgrading Next.js (which also updates the bundled sharp) resolves it.

Denial of service

GHSA-p3m5-59mp-jv5r is a server-side DoS affecting App Router apps that define a Server Action. On Netlify, this has minimal impact: our autoscaling serverless architecture means a malicious request that consumes excessive CPU in one function does not affect other requests. However, active exploitation could increase your function costs. Upgrading Next.js resolves it.

What should I do?

We strongly recommend upgrading next to 15.5.28 or 16.4.1 and redeploying as soon as possible.

Note that any publicly available deploy previews and branch deploys may remain vulnerable until they are automatically deleted. Consider deleting these deploys manually.

Resources

• Next.js Security Update for Upstream Vulnerabilities
• Next.js security advisories

TanStack Start is now 1.0, and Start apps deploy on Netlify. SSR, server routes, server functions, and middleware run on Netlify Functions. It’s also what new Agent Runners projects start with by default.

Start a new app

Deploy the official template, or generate your own:

npx create-tsrouter-app@latest --template file-router --add-ons tanchat,netlify

Deploy an existing app

Install the Netlify plugin:

npm install -D @netlify/vite-plugin-tanstack-start

Then add it to vite.config.ts after tanstackStart():

import { defineConfig } from 'vite'
import { tanstackStart } from '@tanstack/react-start/plugin/vite'
import netlify from '@netlify/vite-plugin-tanstack-start'

export default defineConfig({
  plugins: [tanstackStart(), netlify()],
})

Add a netlify.toml with your build settings:

[build]
  command = "vite build"
  publish = "dist/client"

Develop locally against the real platform

The plugin emulates Netlify in your dev server, so you can build against the same primitives you’ll use in production, without the Netlify CLI:

• Serverless functions and edge functions
• Blobs and Netlify Database
• Cache API and Image CDN
• Redirects, rewrites, and headers
• Environment variables
• AI Gateway

Start with Agent Runners

New projects you start with Agent Runners use TanStack Start 1.0 unless another framework is specified.

Read the TanStack Start guide · Explore the template

Google’s Gemini 4 Argon model is 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 4 Argon model:

import { GoogleGenAI } from '@google/genai';

export default async () => {
    const ai = new GoogleGenAI({});

    const response = await ai.models.generateContent({
        model: 'gemini-4-argon',
        contents: 'How can AI improve my coding?'
    });

    return Response.json(response);
};

Gemini 4 Argon 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 and Agent Runners documentation.

Mistral AI’s Mistral Large 4 model is now available in Netlify Agent Runners. With a 524K-token context window, it’s built for agentic coding and long-context work, making it a good fit for multi-step tasks across larger codebases.

Select it from the model picker to try it today. Learn more in docs.

Meta’s Muse Spark and Muse Wonder models are now available through Netlify’s AI Gateway with zero configuration required. Choose muse-spark-1.1 for coding, computer use, and multimodal perception; muse-spark-1.2 for coding-optimized agentic workflows; muse-spark-1.3 for long-horizon coding and agentic work with cleaner code and fewer tokens; or muse-wonder-1.0 for complex coding tasks, long-running agents, and advanced computer use.

Use the OpenAI SDK directly in your Netlify Functions without managing API keys or authentication. AI Gateway takes care of the setup automatically. Here’s an example using Muse Wonder with the Responses API:

import OpenAI from 'openai';

export default async () => {
    const meta = new OpenAI();

    const response = await meta.responses.create({
        model: 'muse-wonder-1.0',
        input: 'How can AI improve my coding?'
    });

    return Response.json(response);
};

These Meta models also work in Scheduled Functions, Background Functions, and Edge Functions, with Netlify’s caching, rate limiting, and authentication infrastructure available automatically.

Learn more in the AI Gateway documentation and explore the models on Meta’s developer site.

On private projects and sites protected with Netlify team login, your Netlify Functions and Edge Functions can now see who is making the request. The signed-in Netlify user is available as context.user, with their user ID, email address, and when their access expires.

This function returns the signed-in user’s ID, email address, and access expiry as JSON at /whoami, and responds with a 401 when context.user isn’t set:

import type { Config, Context } from '@netlify/functions'

export default async (req: Request, context: Context) => {
  if (!context.user) {
    return new Response('Unauthorized', { status: 401 })
  }

  return Response.json({
    id: context.user.id,
    email: context.user.email,
    expiresAt: context.user.expiresAt.toISOString(),
  })
}

export const config: Config = { path: '/whoami' }

Previously, protecting a site meant Netlify checked who could visit, but your code couldn’t tell who they were. Knowing who’s on the other end meant adding a second login of your own on top.

Now Netlify verifies the visitor at the edge and passes their identity to your code. Because context.user comes from Netlify and not from the request, a visitor can’t impersonate someone else by sending their own headers.

With context.user, you can build on the login your team already uses. Examples like:

• Internal dashboards and admin tools that show each person their own data
• Audit logs that record who made a change or triggered an action
• Approval and review workflows that know who approved what
• Per-person settings, permissions, or feature access inside an internal app

Learn more in the Netlify documentation:

• context.user in Netlify Functions
• context.user in Edge Functions
• Private projects
• Team login protection

You can now subscribe to Netlify events from ChatGPT and set up automations that respond to what’s happening on your sites.

Instead of checking the Netlify dashboard or waiting on an email, you can have ChatGPT act as soon as something happens. Events you can subscribe to include:

• A deploy succeeded
• A build failed
• A form submission came in

For more events to subscribe to, check out our deploy events.

Combine events with Netlify plugin and MCP server

Events get more useful when you pair them with everything else you can already do through the Netlify ChatGPT plugin and Netlify MCP server. For example, you could set up an automation that:

• Reviews new form submissions and flags the ones that need a follow-up
• Summarizes what changed when a production deploy succeeds

Because these automations live in ChatGPT, you can describe what you want in plain language and adjust it as your workflow changes.

Get started

Connect Netlify in ChatGPT, then ask it to subscribe to the events you care about for your project. Learn more in our guide to using Netlify with ChatGPT.