---
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/2/"
last_updated: "2026-08-29T03:47:50.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)
- [
## AI Gateway adds OpenRouter support for more AI model choice
](/changelog/2026-08-06-ai-gateway-openrouter/)
August 6, 2026
- [ai gateway](/changelog/tag/ai-gateway/)
- [ai](/changelog/tag/ai/)
The AI Gateway now supports [OpenRouter](https://openrouter.ai/), giving you access to models from providers beyond Netlify’s direct integrations (OpenAI, Anthropic, Google Gemini).
This partnership opens up models from providers like DeepSeek, Meta, Mistral, Qwen, and xAI, all billed through your existing Netlify credits.
Learn more about our OpenRouter partnership through the [Netlify blog on open models](https://www.netlify.com/blog/build-with-open-models-in-production/).
## Supported models
For a full list of models available on OpenRouter, visit OpenRouter’s [models page](https://openrouter.ai/models).
Note that Netlify only allows requests through OpenRouter for model providers that support a Zero Data Retention (ZDR) policy, meaning your prompts and outputs are never stored nor trained on. Models on OpenRouter that do not have any available provider guaranteeing this policy (at the time of your request) are not available via Netlify.
## Set up OpenRouter for AI Gateway
As with the other providers, Netlify automatically injects `OPENROUTER_API_KEY` and `OPENROUTER_BASE_URL` into your Netlify Functions, Edge Functions, and Preview Server (unless you’ve already set your own values for either).
You can call an OpenRouter-served model using whichever client you prefer:
- **[OpenRouter SDK](https://openrouter.ai/docs/client-sdks/typescript/overview)** (`@openrouter/sdk`): pass `OPENROUTER_BASE_URL` explicitly as `serverURL` when constructing the client, this is the one exception where the base URL isn’t picked up automatically.
- **[OpenAI SDK](https://developers.openai.com/api/docs/libraries)**: works out of the box, no extra config. Just pass a model ID in OpenRouter notation (e.g. `deepseek/deepseek-v4-flash-0731`).
- **[REST API](https://openrouter.ai/docs/api-reference/overview)**: call `${OPENROUTER_BASE_URL}/chat/completions` with a bearer token from `OPENROUTER_API_KEY`.
Whichever client you use, you can find model IDs to pass in the [OpenRouter models directory](https://openrouter.ai/models).
Note that a model listed in OpenRouter’s directory will not work through the AI Gateway if it does not support a Zero Data Retention (ZDR) policy since Netlify only routes to OpenRouter providers with this support.
To learn more about using AI Gateway, check out our [official AI Gateway Netlify docs](https://docs.netlify.com/build/ai-gateway/overview/).
[Permalink to AI Gateway adds OpenRouter support for more AI model choice Permalink](/changelog/2026-08-06-ai-gateway-openrouter/)
- [
## Agent Runners adds OpenCode and AI model controls
](/changelog/2026-08-06-opencode-agent-runners/)
August 6, 2026
- [agent runners](/changelog/tag/agent-runners/)
- [ai](/changelog/tag/ai/)
Through a new partnership with [OpenRouter](https://openrouter.ai/), you can now choose OpenCode as an AI agent with Agent Runners. OpenCode allows you to choose many different AI models, including Kimi, DeepSeek, and GLM.
Learn more about our OpenRouter partnership through the [Netlify blog on open models](https://www.netlify.com/blog/build-with-open-models-in-production/).
Previously, you could only choose Claude, Gemini, or Codex as your AI agent, but now you can choose the OpenCode agent, which offers even more models from different AI providers.
Requests made through OpenCode are only routed to model providers with a Zero Data Retention (ZDR) policy, so your prompts and outputs are never stored.
## AI model selection
As part of this release, you can now also specify which model any agent uses with Agent Runners. Previously, Claude, Gemini, and Codex agents all automatically chose a model for the task you prompted with Agent Runners.
Agents can still auto-select a model for you, but now you can also choose different models for your agents, with these preferences saved just for you on your device.
This means you can experiment with which AI models best fit your needs.
To open your AI model options for Agent Runners, select **agent** near your prompt box.
## Choosing the best AI model for your needs
To help you choose the best AI model for your needs, within Agent Runners you can browse details about each model, including a link to learn more, a visual way to compare cost across all supported models with a 1-5 dot scale, and the option to set an effort level for that model.
To get the most out of your credits, consider the following strategies:
- Use a more expensive, capable model to help you plan your project updates and design a clear prompt with Agent Runners’ [ask mode](https://docs.netlify.com/build/build-with-ai/agent-runners/make-changes-with-agent-runners/#ask-mode), then switch to a cheaper model to implement the changes.
- Experiment with using different AI models for different tasks.
- Be explicit about the functionality you want when using models that are cheaper or set to a lower effort level. These models may fill in placeholder functionality. For example, a model might render a contact page without fully setting up working Netlify Forms, so the page looks complete but doesn’t actually work as expected.
## Learn more
To learn more, check out our docs:
- [Agent Runners overview](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/)
- [Make changes with Agent Runners](https://docs.netlify.com/build/build-with-ai/agent-runners/make-changes-with-agent-runners/)
[Permalink to Agent Runners adds OpenCode and AI model controls Permalink](/changelog/2026-08-06-opencode-agent-runners/)
- [
## Ask mode for Agent Runners
](/changelog/2026-07-30-agent-runners-ask-mode/)
July 30, 2026
- [agent runners](/changelog/tag/agent-runners/)
- [ai](/changelog/tag/ai/)
- [workflow](/changelog/tag/workflow/)
Netlify Agent Runners now have a mode selector. Pick **Ask** and the agent reads, investigates, and answers questions about your project. **Build** is still the default and works exactly as before.
Ask mode is strictly read-only. The agent can’t edit files, run commands, deploy, or change settings. With no build or Deploy Preview, Ask runs are often faster and use fewer credits.
It answers with real context: your repository, your project context, and your project’s Netlify Database. Your data is often the fastest way to answer a question about your app, and Ask mode can query it with no risk of a write.
A few prompts to steal:
- “How many users are in the database?”
- “Walk me through how authentication is implemented in this project. Which files handle it, and where is the token stored?”
- “Our Largest Contentful Paint is bad on mobile. Read the code and tell me what’s most likely responsible.”
- “Plan out how we can migrate to the latest version of Astro.”
Because it’s a mode on the same run, you can switch to Build the moment an answer turns into a task — same run, same context, no re-explaining.
Ask mode is available on all agents, Claude Code, Google Gemini, and OpenAI Codex, in Agent Runners today. See the docs on [Ask and Build modes](https://docs.netlify.com/build/build-with-ai/agent-runners/make-changes-with-agent-runners/#ask-mode).
[Permalink to Ask mode for Agent Runners Permalink](/changelog/2026-07-30-agent-runners-ask-mode/)
- [
## GPT-5.6 Luna and Terra price reduction on AI Gateway
](/changelog/gpt-5-6-luna-terra-price-reduction-ai-gateway/)
July 30, 2026
- [ai gateway](/changelog/tag/ai-gateway/)
- [ai](/changelog/tag/ai/)
GPT-5.6 Luna now costs 80% less and GPT-5.6 Terra is 20% less through Netlify AI Gateway, making both models more cost-efficient for production AI workloads.
These reductions improve the price-performance tradeoff across the GPT-5.6 model family, giving teams more flexibility to choose the right balance of capability and cost for each workload.
Learn more in OpenAI’s announcement, [Advancing the price-performance frontier with GPT-5.6](https://openai.com/index/advancing-the-price-performance-frontier-with-gpt-5-6/).
[Permalink to GPT-5.6 Luna and Terra price reduction on AI Gateway Permalink](/changelog/gpt-5-6-luna-terra-price-reduction-ai-gateway/)
- [
## Keep projects private by default with project visibility
](/changelog/2026-07-28-start-with-private-project-urls/)
July 28, 2026
- [workflow](/changelog/tag/workflow/)
Teams on a [Free, Personal, or Pro plan](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/) now have project visibility settings to ensure that all of your project stay private until you decide to make them public.
More people are shipping prototypes, internal tools, early client work, and projects built with agents. A deploy is often a work in progress, not a publication. Netlify now reflects that distinction.
Project visibility settings allow you to:
- quickly ensure your project stays internal for your Netlify team until you’re ready to launch more publicly.
- ensure that your project stays private for you and your Netlify team.
- choose defaults that keep internal-only projects private, such as for internal apps and tools or sensitive releases.
While project access affects who on your team can access a project from the Netlify dashboard, project visibility impacts who can view your project, both at the live URL and inside of Netlify, and requires Netlify login credentials if a project is set to private.
## Starting defaults
Starting today, all new Netlify teams on a [Free, Personal, or Pro plan](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/) will have their projects set to private by default. This means that new Netlify teams will need to adjust the project visibility of each new site or app to decide when to make them publicly available.
If you have an existing [Free, Personal, or Pro plan](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/) (all credit-based plans), then your starting project visibility settings are set differently to keep the previous default behavior before project visibility settings launched.
This means all your project URLs stay publicly available unless you’ve set up other authentication with code or Netlify’s password protection options.
## Change your project visibility
To change your project’s visibility, you can set a team default for all new and existing projects at: [Team settings > General > Visitor access > Default project visibility](https://app.netlify.com/teams/~/settings/general#default-project-visibility)
To change only one project’s visibility settings: [Project configuration > General > Visitor access > Project visibility](https://app.netlify.com/projects/~/configuration/general/#project-visibility)
## Availability
Project visibility settings are only available for Credit-based [Free, Personal, or Pro plans](https://docs.netlify.com/manage/accounts-and-billing/billing/billing-for-credit-based-plans/credit-based-pricing-plans/).
If you have a Legacy pricing plan, an Enterprise plan, an Open Source plan, you will not find project visibility settings. In this case though, you can still use [password protection](https://docs.netlify.com/manage/security/secure-access-to-sites/password-protection/), [Team login protection (for Enterprise only)](https://docs.netlify.com/manage/security/secure-access-to-sites/password-protection/#protect-your-sites-with-netlify-team-login) or configure [authentication with code](https://docs.netlify.com/manage/security/secure-access-to-sites/overview/#require-password-or-login-credentials).
## Learn more
Learn more about [setting up and managing project visibility](https://docs.netlify.com/manage/security/secure-access-to-sites/project-visibility/) in our docs.
[Permalink to Keep projects private by default with project visibility Permalink](/changelog/2026-07-28-start-with-private-project-urls/)
- [
## Security Update: Multiple vulnerabilities in Nuxt
](/changelog/2026-07-27-nuxt-security-vulnerabilities/)
July 27, 2026
- [security](/changelog/tag/security/)
- [nuxt.js](/changelog/tag/nuxt-js/)
The Nuxt team has disclosed [several security vulnerabilities](https://github.com/nuxt/nuxt/security/advisories) fixed in Nuxt 4.5.1 and 3.21.10, ranging from a high-severity server-side remote code execution (under specific conditions) to lower-severity and development-only issues. Here’s what Netlify customers need to know.
## Vulnerabilities
- [**GHSA-9473-5f9j-94wq**](https://github.com/nuxt/nuxt/security/advisories/GHSA-9473-5f9j-94wq) (High): remote code execution via [server island](https://nuxt.com/docs/4.x/api/components/nuxt-island) props
- [**GHSA-48hr-524c-v5w3**](https://github.com/nuxt/nuxt/security/advisories/GHSA-48hr-524c-v5w3) (Medium): unauthorized component instantiation via server island props
- [**GHSA-hxvh-4h3w-prp9**](https://github.com/nuxt/nuxt/security/advisories/GHSA-hxvh-4h3w-prp9) (High): route rule authorization bypass when a route rule key contains an uppercase character
- [**GHSA-hxcr-hm88-mpq6**](https://github.com/nuxt/nuxt/security/advisories/GHSA-hxcr-hm88-mpq6) and [**GHSA-9pgf-384g-p7mv**](https://github.com/nuxt/nuxt/security/advisories/GHSA-9pgf-384g-p7mv) (High): server component denial of service
- [**GHSA-wm8w-6qjm-cv43**](https://github.com/nuxt/nuxt/security/advisories/GHSA-wm8w-6qjm-cv43) (High): cross-user disclosure of cached payloads (Nuxt 4.x only, 4.4.0 and later)
- [**GHSA-7c4v-fwgw-9rf7**](https://github.com/nuxt/nuxt/security/advisories/GHSA-7c4v-fwgw-9rf7) (Low): dev server path disclosure
- [**GHSA-279x-mwfv-vcqv**](https://github.com/nuxt/nuxt/security/advisories/GHSA-279x-mwfv-vcqv) (Critical, development only): remote code execution in Nuxt DevTools, fixed in `@nuxt/devtools@3.3.1`
## Impact on Netlify
### Remote code execution (GHSA-9473-5f9j-94wq)
This issue **only applies under uncommon conditions**: it requires Vue’s runtime compiler (`vue.runtimeCompiler: true`, which is off by default) and a server island that forwards untrusted input into a component. Few applications meet both conditions, so real-world exposure is limited. We’ve proactively reached out to the very small number of Netlify customers whose projects could potentially be affected.
### Route rule authorization bypass (GHSA-hxvh-4h3w-prp9)
This is a framework-level issue that affects Nuxt apps **regardless of hosting provider**. It is not specific to Netlify. **You’re affected if you use `routeRules` with `appMiddleware` as an authorization gate and any rule key contains an uppercase character**, such as a rule derived from a page like `pages/Admin.vue` or written explicitly as `routeRules: { '/Admin': ... }`. Because routing is case-insensitive by default, the page was served while its route rule (and the middleware guarding it) was silently skipped. This is a regression in the earlier fix for [CVE-2026-53721](https://github.com/nuxt/nuxt/security/advisories/GHSA-mm7m-92g8-7m47), so upgrading only to 4.4.7 or 3.21.7 does not protect you. Upgrade to Nuxt 4.5.1 or 3.21.10, then audit any uppercase route rule keys used for access control.
### Denial of service (GHSA-hxcr-hm88-mpq6, GHSA-9pgf-384g-p7mv)
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.
### Cross-user payload disclosure (GHSA-wm8w-6qjm-cv43)
If you use the `cache`, `swr`, or `isr` route rules on authenticated pages that render user-specific data, a cached payload could be served to the wrong user. **After upgrading, purge any upstream CDN cache (e.g. Akamai or Cloudflare) that may already be holding a leaked payload.** Upgrading alone won’t evict it.
### Development-only issues (GHSA-279x-mwfv-vcqv, GHSA-7c4v-fwgw-9rf7)
The Nuxt DevTools remote code execution and the dev server path disclosure **only affect local development**, not deployed Netlify sites. Still, refresh your lockfile so it picks up `@nuxt/devtools@3.3.1`.
## What should I do?
We strongly recommend upgrading as soon as possible to a patched release:
- `nuxt` 4.5.1 or later (for Nuxt 4)
- `nuxt` 3.21.10 or later (for Nuxt 3)
Running `npx nuxt upgrade --dedupe` also refreshes your lockfile so it pulls in `@nuxt/devtools@3.3.1`, which fixes the critical development-only issue above.
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
- [Nuxt security post](https://nuxt.com/blog/v4-5-security)
- [Nuxt security advisories](https://github.com/nuxt/nuxt/security/advisories)
[Permalink to Security Update: Multiple vulnerabilities in Nuxt Permalink](/changelog/2026-07-27-nuxt-security-vulnerabilities/)
- [
## Netlify Drop updates
](/changelog/2026-07-27-netlify-drop-refresh/)
July 27, 2026
- [workflow](/changelog/tag/workflow/)
[Netlify Drop](https://app.netlify.com/drop) has a refreshed look, with even more support for your questions and guidance on what’s next after you drop your latest site or app.
We first launched Netlify Drop 13 years ago when we introduced the web to a simpler way to deploy your web project and get a custom link for it.
Since that time we’ve learned a lot about how people (and now agents) use Drop. You can learn more from our [official blog post revisiting Netlify Drop](https://www.netlify.com/blog/thirteen-years-of-netlify-drop/) and how it’s evolved over time.
## Same core functionality with more context
The newly improved Drop page keeps the same core functionality, letting you drag and drop your project files or folder, while making it easier for you or an agent to find answers along the way.
For example, did you know Netlify can detect your framework and run a build step for you?
You don’t have to build your project first. If you drop a project folder that uses a framework requiring a build, we’ll direct you to log in first, then take care of the build step for you.
## Try it out
Try it out at [app.netlify.com/drop](https://app.netlify.com/drop).
## After you drop
After you drop a project, claim it to keep your project online and join millions of others, from solo builders to global brands, who manage their sites and apps on Netlify.
After you claim your project, you can keep building in your preferred workflow.
We’ve got you covered with more ways than ever to keep building and deploying:
- [Keep dropping](https://docs.netlify.com/build/build-with-ai/agent-runners/make-changes-with-agent-runners/) to update the same production URL
- [Push your deployed project to a newly created GitHub repo](https://docs.netlify.com/build/git-workflows/create-a-repo-from-netlify/)
- Keep deploying with dev tools, such as our [CLI](https://docs.netlify.com/api-and-cli-guides/cli-guides/get-started-with-cli/) or [API](https://docs.netlify.com/api-and-cli-guides/api-guides/get-started-with-api/)
- [Keep developing with popular AI agents](https://docs.netlify.com/build/build-with-ai/agent-runners/overview/) directly from your Netlify dashboard using Agent Runners
From there you can keep launching with confidence, [undo mistakes (even without Git)](https://docs.netlify.com/deploy/manage-deploys/manage-deploys-overview/#rollbacks), build with a team, and grow to any size, all starting from a drop.
[Permalink to Netlify Drop updates Permalink](/changelog/2026-07-27-netlify-drop-refresh/)
- [
## Claude Opus 5 Now Available in AI Gateway and Agent Runners
](/changelog/claude-opus-5-ai-gateway-agent-runners/)
July 24, 2026
- [ai gateway](/changelog/tag/ai-gateway/)
- [agent runners](/changelog/tag/agent-runners/)
Anthropic’s Claude Opus 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 Opus 5 model:
```
import Anthropic from '@anthropic-ai/sdk';
export default async () => { const anthropic = new Anthropic();
const response = await anthropic.messages.create({ model: 'claude-opus-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 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 Opus 5 Now Available in AI Gateway and Agent Runners Permalink](/changelog/claude-opus-5-ai-gateway-agent-runners/)
- [
## Security Update: Multiple vulnerabilities in React Router
](/changelog/2026-07-23-react-router-security-vulnerabilities/)
July 23, 2026
- [security](/changelog/tag/security/)
- [framework](/changelog/tag/framework/)
The React Router team has disclosed five security vulnerabilities affecting React Router. These issues are patched in React Router 7.18.0 (one issue was patched earlier, in 7.13.0). Here’s what Netlify customers need to know.
## Vulnerabilities
Vulnerability
CVE
Severity
Affected versions
Patched in
Open redirect leading to XSS
CVE-2026-53668
Medium
≥6.30.2 ≤6.30.4, ≥7.9.6 <7.13.0
7.13.0
Unauthenticated Denial of Service in React Router \_\_manifest endpoint
CVE-2026-55685
High
≥7.0.0 <7.18.0
7.18.0
RSCErrorHandler Missing Protocol Validation (XSS)
CVE-2026-53667
Medium
≥7.11.0 <7.18.0
7.18.0
Arbitrary client-side constructor injection via React Router SSR Hydration
CVE-2026-53666
Medium
≥6.4.0 <7.18.0
7.18.0
Unexpected external redirect via untrusted paths
CVE-2026-53669
Medium
≥6.0.0 <7.18
7.18.0
## Impact on Netlify
### Open redirect leading to XSS
Attacker-controlled redirect targets combined with path concatenation and `useNavigate` can escape the intended app path, resulting in open redirects or XSS via `javascript:` URLs. This affects Declarative, Data, and Framework mode apps that pass user-controlled values into navigation APIs.
**Regardless of hosting provider, all apps passing untrusted data into navigation APIs may be vulnerable.**
### Unauthenticated Denial of Service in React Router \_\_manifest endpoint
Deep, attacker-controlled paths can trigger expensive synchronous route matching, blocking the Node.js event loop with a single unauthenticated request to manifest endpoints (`__manifest`, and `*.manifest` in unstable RSC mode). This affects Framework mode with SSR only, including unstable RSC framework mode.
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 function costs.
### RSCErrorHandler Missing Protocol Validation (XSS)
One RSC redirect handling path was missing protocol validation. Apps that redirect to attacker-controlled values may execute dangerous schemes such as `javascript:`. This only affects apps using unstable RSC Data or RSC Framework mode.
**Regardless of hosting provider, all RSC apps redirecting to untrusted values may be vulnerable.** Note that this affects an experimental feature only.
### Arbitrary client-side constructor injection via React Router SSR Hydration
Serialized server errors can carry a subtype that’s resolved against `window` during hydration. Apps that set user-controlled input into `error.name` could have this instantiate browser constructors such as `EventSource`, `WebSocket`, `Worker`, or `Image`. This affects Data and Framework mode SSR hydration.
**Regardless of hosting provider, apps setting user-controlled values into `error.name` may be vulnerable.** This requires an unusual application code path, so real-world impact is expected to be low.
### Unexpected external redirect via untrusted paths
Backslash-based URL forms such as `\\evil.com`, `/\evil.com`, or `\/evil.com` can be interpreted by browsers as cross-origin navigations, bypassing protections that only account for `//`. This affects ``, `useNavigate`, and redirects across Declarative, Data, Framework, and RSC modes.
**Regardless of hosting provider, all apps passing untrusted destinations to ``, `useNavigate`, or redirects may be vulnerable.**
## What should I do?
We strongly recommend upgrading as soon as possible to patched releases:
- `react-router` 7.18.0 or later (all five issues)
- `react-router` 7.13.0 or later addresses the open redirect leading to XSS issue only — upgrade to 7.18.0 for full coverage
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
- [Open redirect leading to XSS (CVE-2026-53668)](https://github.com/remix-run/react-router/security/advisories/GHSA-jjmj-jmhj-qwj2)
- [Unauthenticated Denial of Service in React Router \_\_manifest endpoint (CVE-2026-55685)](https://github.com/remix-run/react-router/security/advisories/GHSA-chx6-hx7r-mcp5)
- [RSCErrorHandler Missing Protocol Validation (XSS) (CVE-2026-53667)](https://github.com/remix-run/react-router/security/advisories/GHSA-h8fp-f39c-q6mh)
- [Arbitrary client-side constructor injection via React Router SSR Hydration (CVE-2026-53666)](https://github.com/remix-run/react-router/security/advisories/GHSA-337j-9hxr-rhxg)
- [Unexpected external redirect via untrusted paths (CVE-2026-53669)](https://github.com/remix-run/react-router/security/advisories/GHSA-wrjc-x8rr-h8h6)
[Permalink to Security Update: Multiple vulnerabilities in React Router Permalink](/changelog/2026-07-23-react-router-security-vulnerabilities/)
[Previous page](/changelog) [Next page](/changelog/page/3)