// Blog

This week in dev: .NET 11 ships, .NET 8 ends, Node.js patches

This week brought two changes that matter to anyone running .NET in production, and one that matters to anyone running Node.js. Microsoft shipped .NET 11 and C# 15 on November 10, and on the same day .NET 8 and .NET 9 reached end of support. A day later, the Node.js project released security fixes for all three supported release lines.

Our short answer: patch Node.js now, plan your move off .NET 8 or 9 this quarter, and choose between .NET 10 and .NET 11 based on how much you want the new C# features, because both are now supported until the same day.

.NET 11 is out

.NET 11.0.0 and SDK 11.0.100 were released on November 10, 2026. It is a Standard Term Support (STS) release, which Microsoft supports for two years, until November 14, 2028, according to the official support policy.

The what's new overview is long. The parts we noticed first: runtime-native async no longer needs a preview flag for projects that target net11.0, the libraries add Zstandard compression and asynchronous validation for data annotations and options, System.Text.Json can write JSON Lines, and the CLI gets dotnet run -e for passing environment variables. The runtime also raises its minimum hardware requirements for x86/x64 and Arm64, so check that before deploying to older servers.

Our take: the detail most teams will miss is in the support table. .NET 10, the current long-term support (LTS) release, also ends support on November 14, 2028. The short-term and long-term releases now retire on the same day, so picking .NET 11 no longer costs you support time.

C# 15 brings union types

C# 15 is the default language version for projects targeting net11.0. The C# 15 release notes list collection expression arguments, union types, closed hierarchies, extension indexers, labeled break and continue, and non-virtual static interface members on older runtimes, with memory safety rules available as a preview.

Union types are the headline. A union is a value that is exactly one of a fixed set of types, and the compiler checks that a switch handles every case:

Pet pet = new Dog("Rex");

string name = pet switch
{
    Dog d => d.Name,
    Cat c => c.Name,
};
Console.WriteLine(name);

public record class Cat(string Name);
public record class Dog(string Name);
public union Pet(Cat, Dog);

Closed hierarchies give a similar guarantee to class hierarchies: mark a base class closed and only its own assembly can derive from it, so a switch over its subclasses needs no default arm.

Our take: this is the C# change we expect to use most in business code. Outcomes like "paid", "out of stock" and "payment declined" can become types the compiler checks, instead of status strings and nullable fields that drift apart.

.NET 8 and .NET 9 are now out of support

Both versions reached end of support on November 10, 2026, as Microsoft announced in June. The final patches are 8.0.34 and 9.0.23, and the support policy page now lists both as out of support. In practice that means Microsoft no longer ships fixes or updates for them. Your apps keep running, but new vulnerabilities will not be patched.

Our take: .NET 8 was an LTS release, so a lot of business software still runs on it. Moving to .NET 10 or 11 is normally a framework upgrade plus fixing breaking changes, not a rewrite, but it needs testing time. Put it on this quarter's plan rather than waiting for the first unpatched security advisory.

Node.js patches 16 vulnerabilities in 22, 24 and 26

On November 11 the Node.js project shipped security releases for every supported line: 22.23.5, 24.22.3 and 26.13.1. They fix 16 vulnerabilities, seven rated high, and update the bundled llhttp, undici and sqlite dependencies.

Most of the high-severity issues are in HTTP/2 and TLS handling, and several can be triggered by an unauthenticated client: crashing the server, leaking memory and file descriptors, or, in one HTTPS case, reading memory that belongs to other connections. That HTTPS bug does not affect cleartext node:http. The project also repeats that end-of-life Node.js versions are always affected when a security release occurs.

Five of the sixteen reports credit a researcher working with Anthropic's Claude. Our take: AI-assisted security research is now finding real, high-severity bugs in core runtimes, and we expect that to mean more security releases, not fewer. Upgrading Node should be a routine job, not a project.

If Node terminates HTTPS or HTTP/2 itself, upgrade today. If it sits behind a reverse proxy or load balancer, some of these bugs may not be reachable, but we would still upgrade this week rather than spend the time proving it.

What to do this week

  • Upgrade Node.js to 22.23.5, 24.22.3 or 26.13.1, including Docker base images and CI runners.
  • List every service still on .NET 8 or 9 (check the target framework in project files and the runtime in your container images) and give each one an upgrade date.
  • Pick .NET 10 if you want a release with a year of production patches behind it, or .NET 11 if you want C# 15. Both are supported until November 14, 2028.
  • If your code is full of switches on status values, try union types on one small, isolated piece first.

If you have a .NET 8 app that needs an upgrade plan, or a Node.js backend you want checked after this week's patches, tell us what you are running and we will help you work out the next step.