> 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/cortex-xdr-3.x-rn/cortex-xdr-release-information/previous-maintenance-releases/xdr-collectors/xdr-collectors-152-major-318.md).

# XDR Collectors 1.5.2 (Major)

The XDR Collectors major release for Windows 1.5.2.2326 and Linux 1.5.2.2173 was released as part of the following releases of Cortex XSIAM:

* 3.17 on January 28, 2026
* 3.18 on May 3, 2026

The following table describes the changes integrated for this release:

| ISSUE                                 | DESCRIPTION                                                                                                                                                                                                                                                                                                                       |
| ------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| CPATR-32437, CPATR-32546, CPATR-32547 | Upgraded the SQLite package to version (3.50.4) for both Linux and Windows XDR Collectors. This update addresses known vulnerabilities on previous SQLite versions.                                                                                                                                                               |
| CPATR-33046                           | Resolved an issue where XDR Collectors failed to start at initialization due to a third-party package.                                                                                                                                                                                                                            |
| CPATR-33166                           | Updated the "No incoming data" warning string to specify the associated application, for example, "winlogbeat: No incoming data for more than 7 days". This improves visibility by clarifying whether the alert refers to Winlogbeat or Filebeat data streams.                                                                    |
| CPATR-33262                           | Fixed a validation logic error where XDR Collectors incorrectly displayed an "Error" status when only Filebeat or Winlogbeat was configured. The collector now accurately reflects a "Connected" status based on the active YAML configuration, eliminating false error indications while data ingestion is functioning properly. |
| CPATR-34604                           | Resolved an issue where XDR Collectors failed to retrieve MAC addresses or hardware IDs, causing redundant re-registrations. This fix ensures stable device identification and prevents duplicate collector entries in the console.                                                                                               |


---

# 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/cortex-xdr-3.x-rn/cortex-xdr-release-information/previous-maintenance-releases/xdr-collectors/xdr-collectors-152-major-318.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.