c92b6eff99
* Update releases.md * Update README.md * Update releases-index.json * Update README.md * Update 9.0 releases.json * Update README.md * Update 9.0 install-linux.md * Update install-macos.md * Update 9.0 install-windows.md * Update 9.0 cve.md * Create 9.0.8.md * Create 9.0.109.md * Create release.json * Update 8.0 releases.json * Update 8.0 README.md * Update 8.0 cve.md * Update 8.0 install-linux.md * Update 8.0 install-macos.md * Update 8.0 install-windows.md * Create 8.0.19.md * Create 8.0.119.md * Create 8.0.316 * Create 8.0 release.json * Update releases-index.json * Rename 8.0.316 to 8.0.316.md
2.2 KiB
2.2 KiB
.NET 9 CVEs
The .NET Team releases monthly updates for .NET 9 on Patch Tuesday. These updates often include security fixes. If you are on an older version, your app may be vulnerable.
Your app needs to be on the latest .NET 9 patch version to be secure. The longer you wait to upgrade, the greater the exposure to CVEs.
Which CVEs apply to my app?
Your app may be vulnerable to the following published security CVEs if you are using an older version.
- 9.0.8 (August 2025)
- No new CVEs.
- 9.0.7 (July 2025)
- No new CVEs.
- 9.0.6 (June 2025)
- 9.0.5 (May 2025)
- 9.0.4 (April 2025)
- 9.0.3 (March 2025)
- 9.0.2 (February 2025)
- No new CVEs.
- 9.0.1 (January 2025)
- 9.0.0 (November 2024)
The CVE exposure is cumulative. For example, 8.0.0 users may be vulnerable to the CVEs present in 9.0.0 and newer releases. Similarly, 9.0.3 users may be vulnerable to the CVEs present in 9.0.4 and newer releases. The latest release is not vulnerable to any published CVEs.