> 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.md).

# XDR Collectors

Cortex XDR includes an XDR Collectors version with each release that contains new features and enhancements. There can be additional XDR Collectors maintenance releases before the next Cortex XDR release that are compatible with the released version.

## XDR Collectors Compatibility

The table below lists the most recent XDR Collectors versions that are compatible with Cortex XDR starting from the Cortex XDR 3.5 release.

| XDR Collectors Version | Cortex XDR Version | Release Date (GA)  |
| ---------------------- | ------------------ | ------------------ |
| 1.5.3 (Current)        | 3.19               | July 20, 2026      |
| 1.4.3 (Current)        | 3.19               | July 20, 2026      |
| 1.5.2                  | 3.18               | May 3, 2026        |
| 1.4.3                  | 3.18               | May 3, 2026        |
| 1.5.2                  | 3.17               | January 28, 2026   |
| 1.5.1                  | 3.17               | January 25, 2026   |
| 1.4.3                  | 3.17               | January 25, 2026   |
| 1.5.1                  | 3.16               | November 9, 2025   |
| 1.4.3                  | 3.16               | November 9, 2025   |
| 1.5.1                  | 3.15               | August 13, 2025    |
| 1.5.1                  | 3.15               | July 29, 2025      |
| 1.5.0                  | 3.15               | July 20, 2025      |
| 1.4.3                  | 3.15               | July 20, 2025      |
| 1.5.0                  | 3.14               | April 27, 2025     |
| 1.4.3                  | 3.14               | April 27, 2025     |
| 1.5.0                  | 3.13               | February 16, 2025  |
| 1.4.3                  | 3.13               | February 16, 2025  |
| 1.4.2                  | 3.13               | February 2, 2025   |
| 1.4.2                  | 3.12               | September 22, 2024 |
| 1.4.2                  | 3.11               | July 22, 2024      |
| 1.4.1                  | 3.11               | June 30, 2024      |
| 1.4.1                  | 3.10               | April 14, 2024     |
| 1.4.1                  | 3.9                | February 11, 2024  |
| 1.4.1                  | 3.8                | October 15, 2023   |
| 1.4.0                  | 3.7                | June 25, 2023      |
| 1.4.0                  | 3.6                | March 5, 2023      |
| 1.3.0                  | 3.5                | December 4, 2022   |


---

# 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.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.