.NET and .NET Framework July 2024 servicing releases updates

Tara Overfield

Rahul Bhandari (MSFT)

Welcome to our new combined .NET servicing updates for July 2024. To help streamline and help you keep up to date with the latest service releases we have decided to combine our update posts around both .NET & .NET Framework so you can find all the information in one convenient location on the blog. Don’t forget that you can find updates about .NET previews on GitHub, specifically for .NET 9. Let’s get into the latest release of .NET & .NET Framework, here is a quick overview of what’s new in these releases:

Security improvements

This month you will find two CVEs that have been fixed this month:

CVE # Title Applies to
CVE-2024-30105 .NET Denial of Service Vulnerability .NET 8.0
CVE-2024-35264 .NET Remote Code Execution Vulnerability .NET 8.0
CVE-2024-38081 .NET Remote Code Execution Vulnerability .NET 6.0, .NET Framework 2.0, 3.0, 3.5, 4.6.2, 4.7, 4.7.1, 4.8, 4.8.1
CVE-2024-38095 .NET Remote Code Execution Vulnerability .NET 8.0, .NET 6.0

Note: There are no new security improvements for .NET Framework this release.

.NET July 2024 Updates

Below you will find a details list of everything from the .NET release for July 2024 including .NET 6.0.32 and .NET 8.0.7:

.NET 6.0 .NET 8.0
Release Notes 6.0.32 8.0.7
Installers and binaries 6.0.32 8.0.7
Container Images images images
Linux packages 6.0.32 8.0.7
Known Issues 6.0 8.0

.NET Improvements

Share feedback about this release in the Release feedback issue.

.NET Framework July 2024 Updates

This month, there are security and non-security updates in these releases, be sure to browse our release notes for .NET Framework for more details.

See you next month

Let us know what you think of these new combined service release blogs as we continue to iterate to bring you the latest news and updates for .NET.


Leave a comment

  • Xuhua Chen 1

    Link “release notes for .NET Framework” Error 404

  • Mystery Man 0

    Hello, .NET team.

    Thanks for not releasing an update last month. I enjoyed not having to deal with its headaches. I’d have a bash if I knew you weren’t going to release an update. Instead, I was in a state of constant fear as to when the delayed update will come.

    .NET Framework 3.5 and 4.8 updates are mostly fine. I don’t trust them, but they haven’t done anything wrong so far. (I don’t trust them because their digital signature shows they’ve been ready to go out the door one or two months before.)

    .NET 6 and 8, however, are the headache. Windows Update, Visual Studio, and Visual Studio Code all insist on their divergent ways of installing the latest .NET update. Windows Update just installs the latest binary package. Visual Studio insists on installing a system-breaking stub called “Microsoft .NET SDK 8.0.xxx (x64) for Visual Studio.” Sometimes, I just can’t uninstall an old .NET version without reinstalling Windows. Visual Studio Code is the worst. The nightmarish extension called “.NET Install Tool” dances to nobody’s tune. This chaotic state of affairs is analogous to how Jews, Christians, and Muslims worship the same God, but can’t stand each other.

Feedback usabilla icon