Changelog

Here are some Agent Runners improvements that all people with Credit-based pricing plans can enjoy:

Shareable agent run links

You can now link directly to an agent run to share it with your team or bookmark for later review.

Agent Runners available no matter how you deploy

Agent Runners now supports static projects without build steps. Previously, projects without a build step couldn’t use Agent Runners.

Improved diff view performance

By default, the diff view now loads only the first 50 changed files with an option to load more. This improves performance for large projects.

Feedback welcome

Keep sharing your product feedback about Agent Runners in the feedback form at the bottom of our Agent Runners docs page.

And don’t forget that while you can run multiple agent runs and do other work while they run, you can also play a Netlify game while you wait for the agent to finish.

A denial-of-service (DoS) vulnerability (CVE-2026-23864, CVSS 7.5) has been disclosed affecting React Server Components (RSCs), a feature used by Next.js and other React metaframeworks. A malicious payload can cause memory exhaustion or excessive CPU consumption. Next.js has also disclosed two unrelated medium-severity CVEs (CVE-2025-59471, CVE-2025-59472) patched in the same releases. Here’s what Netlify customers need to know.

Impact on Netlify

Nominally, this is a server-side DoS vulnerability. However, on Netlify this has minimal impact: our autoscaling serverless architecture means that a malicious request resulting in a crashed or hung function does not affect other requests. However, active exploitation could increase your function costs.

Affected frameworks

All RSC frameworks are affected:

• Next.js (see version table below)
• React Router 7 (if using RSC preview)
• Waku
• @parcel/rsc
• @vitejs/plugin-rsc

Astro, Gatsby, and Remix are not affected.

React affected versions

See the React blog post for full details.

Next.js affected versions

See the Next.js advisory for full details.

What should I do?

If any of your projects are using an affected version, we recommend upgrading as soon as possible to a patched release.

For Next.js 13.x and 14.x users: patches are not planned for these versions. Consider upgrading to Next.js 15.x or 16.x.

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

Resources

• React CVE-2026-23864
• React blog post
• Next.js security advisory

The React Router team has disclosed six security vulnerabilities affecting React Router and Remix. Here’s what Netlify customers need to know.

Vulnerabilities

Impact on Netlify

CVE-2025-61686 (path traversal)

This vulnerability affects @react-router/node, @remix-run/node, and @remix-run/deno. These packages are not used on Netlify, therefore Netlify projects are not affected.

CVE-2025-68470 (open redirect)

Apps with unsafe uses of React Router navigation APIs may be hijacked to redirect to arbitrary origins.

Regardless of hosting provider, all apps constructing paths from untrusted user input may be vulnerable.

CVE-2026-22030 (CSRF)

Actions and experimental RSC Server Functions can be triggered by cross-origin form submissions, allowing an attacker to execute actions on behalf of authenticated users.

Regardless of hosting provider, all apps may be vulnerable.

CVE-2025-59057, CVE-2026-22029, and CVE-2026-21884 (XSS)

These are cross-site scripting (XSS) vulnerabilities. For example, in CVE-2026-22029 actions and experimental RSC Server Functions performing a redirect to a path constructed from untrusted user input may be hijacked to execute arbitrary JavaScript in the browser.

Regardless of hosting provider, all apps passing untrusted data into certain APIs may be vulnerable. (The Remix team has left this intentionally vague.)

What should I do?

If any of your projects are using any affected version listed above, we strongly recommend upgrading as soon as possible to patched releases:

• react-router 7.12.0 or later (for React Router 7.x)
• react-router 6.30.2 or later (for React Router 6.x)
• @remix-run/react 2.17.4 or later
• @remix-run/server-runtime 2.17.4 or later

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

The Node.js team has released a security update addressing a denial-of-service vulnerability affecting applications that use async_hooks (including in dependencies). Here’s what Netlify customers need to know.

Vulnerability

When async_hooks are enabled on certain versions of Node.js, a stack overflow causes the Node.js process to exit immediately rather than throw a catchable error. This bypasses try-catch blocks and uncaught exception handlers entirely.

A malicious actor could send a crafted payload to crash a server.

Note that many common tools and frameworks use async_hooks under the hood, notably APM and tracing tools (e.g. DataDog, NewRelic, OpenTelemetry) as well as Next.js App Router and other React Server Components implementations. You can find more details on that here.

Impact on Netlify

This is a server-side denial-of-service (DoS) vulnerability. On Netlify, this has minimal impact: our autoscaling serverless architecture means that a malicious request resulting in a crashed or hung function does not affect other requests. However, active exploitation could increase your cold starts and your function costs.

Note that Node.js used during your project’s build is not impacted at all.

What should I do?

If you have opted your Netlify Functions into Node.js 18, we recommend upgrading to Node.js 20 or later. Node.js 18 reached end-of-life in April 2025 and thus will not be patched.

Otherwise, there is no action for you to take. Although this CVE’s impact to Netlify sites is limited, deployed Netlify Functions will be updated to patched Node.js versions automatically on a rolling basis.

For completeness, please note that the Node.js version used during your project’s build is not relevant to this CVE. There is no action for you to take and this will not be automatically patched.

Resources

• Node.js security release announcement
• Netlify Functions Node.js version configuration

The Svelte team has disclosed five CVEs affecting the Svelte and SvelteKit ecosystem. Here’s what Netlify customers need to know.

Vulnerabilities

• CVE-2026-22775: Memory/CPU exhaustion in devalue (5.1.0–5.6.1)
• CVE-2026-22774: Memory exhaustion in devalue (5.3.0–5.6.1)
• CVE-2026-22803: Server crash in @sveltejs/kit (2.49.0–2.49.4)
• CVE-2025-67647: Server crash and SSRF in @sveltejs/kit (2.44.0–2.49.4) and @sveltejs/adapter-node (2.19.0–2.49.4)
• CVE-2025-15265: XSS in svelte (5.46.0–5.46.3)

Impact on Netlify

CVE-2026-22775, CVE-2026-22774, and CVE-2026-22803

These are server-side denial-of-service (DoS) vulnerabilities. On Netlify, these have minimal impact: our autoscaling serverless architecture means that a malicious request resulting in a crashed or hung function does not affect other requests. However, active exploitation could increase your function costs.

In addition, note that only sites using the experimental Remote Functions feature are affected.

CVE-2025-67647

As above, this DoS vulnerability involves intentionally “crashing” a server. On Netlify, this has minimal impact.

The SSRF vulnerability affects a @sveltejs/adapter-node, which is not used by apps deployed to Netlify.

CVE-2025-15265

This is a client-side cross-site scripting (XSS) vulnerability. Regardless of hosting provider, all apps using the experimental hydratable with unsanitized user-controlled keys are vulnerable.

What should I do?

Although the impact to Netlify sites is limited in this case, we always strongly recommend upgrading as soon as possible to patched releases:

• devalue 5.6.2 or later
• @sveltejs/kit 2.49.5 or later
• @sveltejs/adapter-node 5.5.1 or later
• svelte 5.46.4 or later

Resources

• Svelte team disclosure

OpenAI’s GPT-5.2-Codex 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. The AI Gateway handles everything automatically. Here’s an example using the GPT-5.2-Codex model:

import OpenAI from 'openai';

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

    const response = await openai.responses.create({
        model: 'gpt-5.2-codex',
        input: 'How does AI work?'
    });

    return new Response(JSON.stringify(response), {
        headers: { 'Content-Type': 'application/json' }
    });
};

GPT-5.2-Codex is available across Background Functions, Scheduled 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.

While Agent Runners take care of tasks on your site, you can now play games right in the UI. We’ve brought the same beloved build-time games to the Agent Runner page, so you can flip tiles, plan snake, install other games, or even create your own while your agent runs in the background.

A little delight, now everywhere you wait.

Learn more about the Netlify Entertainment System.

The third-party Prerender.io service for advanced prerendering is now available as an extension for all Netlify customers.

Previously, you needed a Netlify Pro plan or higher to set up Prerender.io with Netlify’s legacy in-app prerendering feature.

Prerender.io offers advanced configuration options and the Prerender.io dashboard. Learn more about the Prerender.io extension from the extension details page.

If you previously set up Prerender.io using Netlify’s legacy in-app prerendering feature, you need to update your configuration to continue using it this year. Learn more about your next steps and how to check if you need to update your configuration.

To check if your project still needs prerendering, see our prerendering needs checker documentation.

Configuration updates required for existing users

If you have a Netlify Pro plan and you set up the Prerender.io service with Netlify’s legacy prerendering feature (most likely before January 6, 2026), you’ll need to update your configuration to continue using it this year.

To check if your project is using Netlify’s legacy in-app prerendering feature, go to Project configuration > Build & deploy > Post processing > Prerendering from your Netlify project dashboard to see if the legacy prerendering feature is enabled.

Updates are required because Prerender.io no longer relies on Netlify’s legacy in-app prerendering feature, which is being deprecated and will stop working later this year.

Follow our migration steps to update your configuration before these key dates:

Learn more about this migration process in this migration post.

You can also reach out to Netlify Support for help.

Google’s Gemini 3 Flash Preview is now available through AI Gateway. You can call this model from Netlify Functions without configuring API keys; the AI Gateway provides the connection to Google for you.

Example usage in a Function:

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

export default async (request: Request, context: Context) => {
  const ai = new GoogleGenAI({});

  const response = await ai.models.generateContent({
    model: 'gemini-3-flash-preview',
    contents: 'How does AI work?'
  });

  return new Response(JSON.stringify({ answer: response.text }), {
    headers: { 'Content-Type': 'application/json' }
  });
};

This model works across any function type and is compatible with other Netlify primitives such as caching and rate limiting, giving you control over request behavior across your site.

See the AI Gateway documentation for details.