Migration13 November 2026

Still on IdentityServer4 in 2026? What's unpatched, and your ways out

IdentityServer4 reached end of life on 13 December 2022. One known security flaw has no fix for it, and future flaws won't get one either. How to check your own app, and the four realistic ways out.

IdentityServer4 was the default way to run your own OpenID Connect server on .NET for years, and plenty of production systems still sign users in through it. This post covers what "end of life" means for it in practice, the one known flaw that has no fix, how to check your own app, and the realistic ways out.

A note first. We build Vord, which is one of the options at the end. Everything about IdentityServer4 below is quoted from Duende, GitHub or NuGet, with links at the bottom and the date we read them. If it matters to your decision, open the links and check again.

The short version

  • IdentityServer4 reached end of life on 13 December 2022. Its repository is archived, and the last version is 4.1.2.
  • One known security flaw, an open redirect (CVE-2024-39694), affects every IdentityServer4 version and has no fix. There is a workaround.
  • More important than that one flaw: any flaw found from now on won't be fixed either.
  • NuGet marks the package as legacy and vulnerable, and recent .NET SDKs warn about it when you restore.
  • The ways out are Duende IdentityServer, OpenIddict, Keycloak or a hosted service, or Vord. Which one fits depends mostly on how much code you want to keep.

What end of life means here

Duende's own upgrade guide says it plainly: "IdentityServer4 reached its end of life (EOL) on December 13, 2022." The GitHub repository has since moved to the DuendeArchive account and is archived, so it's read-only. On NuGet, the IdentityServer4 package is unlisted and marked as deprecated with the reason "Legacy", and NuGet suggests Duende.IdentityServer instead.

The last version, 4.1.2, was built for .NET Core 3.1, which reached its own end of support on the same day, 13 December 2022. A newer .NET app can still reference the package, but the IdentityServer4 code inside it gets no fixes, whatever runtime you run it on.

The flaw with no fix

In July 2024, Duende published an open-redirect advisory, CVE-2024-39694 (GitHub advisory GHSA-ff4q-64jc-gx98, rated medium). An attacker can craft a URL that some IdentityServer functions wrongly treat as local and trusted. If your login UI redirects to it, some browsers will follow it to a site the attacker controls.

The affected code is on the usual path. The advisory names GetAuthorizationContextAsync and IsValidReturnUrl on the interaction service, and says the default UI templates use them on the login, challenge and consent pages.

The advisory is also clear about what the flaw doesn't do: by itself, it doesn't hand over passwords, authorization codes or tokens. It could be used as part of a phishing attack to steal them.

Duende fixed it in Duende.IdentityServer 7.0.6, 6.3.10, 6.2.5, 6.1.8 and 6.0.5. For IdentityServer4, the vulnerable range is <= 4.1.2 with no patched version, and the advisory says IdentityServer4 is "no longer supported and will not be receiving updates".

If you can't move yet, the advisory gives a workaround: validate return URLs in your login UI with IUrlHelper.IsLocalUrl from ASP.NET Core 5.0 or later. That closes this flaw. It doesn't help with the next one.

How to check your own app

Run this in the folder of your IdentityServer host:

dotnet list package --vulnerable --include-transitive

If the host references IdentityServer4 4.1.2, it's listed with the two advisories GitHub holds for this flaw (GHSA-ff4q-64jc-gx98 and GHSA-55p7-v223-x366). From the .NET 8 SDK on, NuGet Audit also warns about known vulnerabilities on every restore, so if your build output shows a warning for IdentityServer4, that's this one.

While you're there, note three things you'll need for any of the options below: which user store you use (ASP.NET Core Identity or something custom), how many clients and APIs trust the server, and how much custom code sits on top of IdentityServer4.

The ways out

Duende IdentityServer: the upgrade path

Duende IdentityServer comes from the same team, and Duende publishes an official guide for upgrading from IdentityServer4 to the current version. Your code changes least on this route: the concepts, the configuration model and most of the API carry over.

The trade-off is the licence. Duende IdentityServer is commercial software, with a free Community Edition that comes with conditions. Our Duende cost post quotes the current prices and the Community Edition rules from Duende's own pages.

OpenIddict: a free library, you build more

OpenIddict is an open-source OpenID Connect library for ASP.NET Core under the Apache 2.0 licence. It handles the protocol, and you build the server around it: the login pages, the admin screens, and how clients and users are managed. It suits teams that want to own all the code and don't mind the extra work.

Keycloak or a hosted service: a different stack

Keycloak is an open-source identity server written in Java, which you run and update yourself. Hosted services such as Microsoft Entra External ID and Auth0 take the operations away, and you pay per monthly active user. All of them work with .NET apps through standard OpenID Connect, but your users' passwords and your custom IdentityServer code don't carry over automatically. The cost post compares all three.

Vord

Vord is the identity service we build. It's in early access and releases on 1 December 2026. It's hosted, and self-hosting is available on request. It's built on OpenIddict and ASP.NET Core Identity, and adds organizations, per-organization SSO and SCIM for B2B SaaS.

What matters most for an IdentityServer4 move is passwords. IdentityServer4 is often paired with ASP.NET Core Identity, and on .NET Core 3.1 ASP.NET Core Identity stored passwords as V3 hashes (HMAC-SHA256, 10,000 iterations). That's one of the two formats our tests import and then sign in with, so those users can keep their passwords. This doesn't apply to the older V2 format from ASP.NET Identity 2.x, or to a custom user store.

Moving to Vord isn't a drop-in swap. Your apps point at a new server, everyone signs in once after the switch, and your APIs will probably need code changes, because Vord's access tokens have no audience and Vord has no custom API scopes. Vord is also new and has no track record yet. Our migration post covers what carries over and what changes, step by step.

When staying put is still reasonable

Not every IdentityServer4 install needs to move this month. If it only signs in your own staff on a private network, and you've added the IsLocalUrl check, the exposure from today's known flaw is small. What doesn't change is that every future flaw stays unfixed, and you'll only find out from an advisory. If customers sign in through it, or you sell to companies that send security questionnaires, plan the move now rather than after the next advisory.

If you want to talk through a move to Vord, join the early-access list.

Sources

Read on 2026-11-13 from the raw pages, APIs or files: