> 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/cloud-posture-management-rn/cortex-cloud-posture-management-release-information/previous-maintenance-releases/broker-vm/broker-vm-31058-major.md).

# Broker VM 31.0.58 (Major)

The following table describes the changes integrated on the Broker VM major version 31.0.58 released on May 17, 2026 as part of the Cortex Cloud 2.1 release. This version replaces the previous version released on May 3, 2026 as the major version for the release. The release is divided into three deployments: May 3, 2026, May 17, 2026, and May 31, 2026.

| ISSUE/FEATURE                  | DESCRIPTION                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
| ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Broker VM upgrade enhancements | This update improves the reliability and stability of the Broker VM upgrade process. We’ve addressed several underlying issues to ensure a smoother transition between versions with reduced downtime.                                                                                                                                                                                                                                                                                                                  |
| CRTX-242789                    | <p>Resolved issues affecting static route management on Broker VM versions older than 31.0.58, while updating supported routing commands.</p><ul><li>Fixed routing service restarts: Fixed an issue where the <code>restart\_routes</code> command failed to execute, preventing static routes from being successfully configured or restarted. This command is now fully functional.</li><li>Deprecated route command: The legacy <code>route</code> command has been deprecated and is no longer supported.</li></ul> |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cloud-posture-management-rn/cortex-cloud-posture-management-release-information/previous-maintenance-releases/broker-vm/broker-vm-31058-major.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
