> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/8.x/8.3ce/cortex-xdr-agent-8.3-ce-release-information/addressed-issues-in-cortex-xdr-agent-8.3-ce/cortex-xdr-agent-8.3.102-ce-addressed-issues.md).

# Cortex XDR agent 8.3.102-CE addressed issues

The following issues have been resolved in this release.

| **Issue**                          | **Description**                                                                                                         |
| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| <p>CPATR-31056</p><p>(Windows)</p> | Fixed an issue that may occur on rare occasions when running a scan.                                                    |
| <p>CPATR-28903</p><p>(Windows)</p> | Fixed an issue to resolve a misleading ProductType when using Windows Enterprise multi-session OS builds.               |
| <p>CPATR-28368</p><p>(Windows)</p> | Fixed an issue to improve the Cortex XDR agent security and stability posture.                                          |
| <p>CPATR-27550</p><p>(Windows)</p> | Fixed an issue to improve the Cortex XDR agent security and stability posture.                                          |
| <p>CPATR-27148</p><p>(Windows)</p> | Fixed an issue that in rare cases may generate a false indication of a successful security event.                       |
| <p>CPATR-26540</p><p>(Linux)</p>   | Improvement made to the Cortex XDR agent stability posture.                                                             |
| <p>CPATR-26349</p><p>(MacOS)</p>   | Fixed an issue to ensure that USB device control remains read only once enabled.                                        |
| <p>CPATR-26119</p><p>(Linux)</p>   | Fixed an issue where in a rare scenario, the SPMD process may demonstrate a high CPU consumption during content update. |
| CPATR-25760                        | Fixed an issue that in rare circumstances may cause the NMAP distributed network scan to function incorrectly.          |
| <p>CPATR-25193</p><p>(Linux)</p>   | Fixed an issue that may occur after AWS Kubernetes Bottlerocket cluster is upgraded to 1.30                             |
| <p>CPATR-23086</p><p>(Windows)</p> | Improvement made to the Cortex XDR agent security and stability posture.                                                |
| <p>CPATR-18158</p><p>(Windows)</p> | Fixed an issue that may occur when the Java Deserialization Protection module is enabled on a machine.                  |


---

# 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://cortex-docs.paloaltonetworks.com/8.x/8.3ce/cortex-xdr-agent-8.3-ce-release-information/addressed-issues-in-cortex-xdr-agent-8.3-ce/cortex-xdr-agent-8.3.102-ce-addressed-issues.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.