> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/release-notes/notices/critical-.net-8-security-update-oct-14th-2025.md).

# Critical .NET 8 Security Update (Oct 14th, 2025)

Published on October 22nd, 2025

Regarding the critical security update released by Microsoft for .NET 8 and higher, tracked as GHSA-5rrx-jjjq-q2r5 (CVSS 9.9 / 10). This affects the .NET runtime used by Frends Agents.

**Action required for on-premises installations.**

This update requires action from customers who host Frends components in their own infrastructure.

All affected Frends Agents hosted by Frends are patched automatically to apply the security update. This causes a very short outage on the Agent when the Agent is restarted to take the patch into use.

Update the .NET Runtime and SDK on each on-premises server to the latest release.

**How to perform the update:**

1. Check the installed .NET SDK and runtime versions with the command: **dotnet --info**
2. Check the Host section version, it should be at least **8.0.21**.
3. If it is anything lower, we strongly recommend downloading and installing the ASP.NET Core Runtime 8.0.21 or the suitable SDK version which contains the 8.0.21 runtime. After installing the update, restart the Frends Agent and Control Panel services on the server.

The vulnerability is not present in any code or components delivered by Frends, meaning that the Frends Control Panel or Agents themselves do not need to be updated, but rather the .NET runtime installed on the servers hosting Frends components.

**Note:** Frends has used .NET 8 since Frends 5.7; earlier versions use .NET 6. Microsoft has not confirmed .NET 6 to be affected at this time.

The security advisory: <https://github.com/advisories/GHSA-5rrx-jjjq-q2r5>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.frends.com/release-notes/notices/critical-.net-8-security-update-oct-14th-2025.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
