> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/ce-release-notes/prisma-tm-cloud-compute-edition-release-information/release-notes-34-04-160.md). # 34.04 (Build 34.04.160) The following table has the release details: | Build | 34.04.160 | | ------------ | ---------------------------------------------------------------- | | Code name | Quinn Update 4 | | Release date | May, 2026 | | Type | Minor release | | SHA-256 | 4b5a72a26df7c8d573a349d70edbcdea0f39fe6164e0d9e1518c8ec67ed57ab7 | Review the [system requirements](https://docs.prismacloud.io/en/compute-edition/34/admin-guide/install/system-requirements) to learn about the supported operating systems, hypervisors, runtimes, tools, and orchestrators. ## Upgrade from Previous Releases ### Upgrade Defenders With the `v34.00` release, the [supported Defender releases (n, n-1, and n-2)](https://docs.prismacloud.io/en/compute-edition/34/admin-guide/upgrade/support-lifecycle) are `v34`, `v33`, and `v32` respectively. In addition, Prisma Cloud will not restrict the usage of Defender versions or REST API calls from the n-3 releases. So, the current release will allow Defenders and REST API calls from release `v31` also. Failure to upgrade Defenders below release `v31`, such as `v30.03`, will result in disconnection of the Defenders from the Console. However, to maintain full support, you must upgrade your Defenders to a `v32.xx` or later release. To summarize, the level of support for the different versions of Defenders is as follows: * Defender versions 34.xx, 33.xx, and 32.xx have full support * Defender versions 31.xx are functional (will be able to connect to version 34.00 Console) but support is not available for such Defenders * Defender versions previous to 31.00, such as 30.03, are neither supported nor functional (cannot connect to version 34.xx Console) ### Upgrade the Prisma Cloud Console With the `v34.00` release, the [supported Console releases (n, n-1, and n-2)](https://docs.prismacloud.io/en/compute-edition/34/admin-guide/upgrade/support-lifecycle) are `v34`, `v33`, and `v32` respectively. Defenders from the n-3 release will remain functional as described above. You can upgrade the Prisma Cloud console directly from any n-1 or n-2 version to n. For example, with `v34` as n and `v33` as n-1, you can upgrade directly from `33.01.137` to `34.00.141`. You can also upgrade directly from an n-2 version (`32.00.161`, `32.01.128`, `32.02.127`, `32.03.123`, `32.04.113`, `32.05.124`, `32.06.113`, `32.07.123`) to `34.00.141`. ## Enhancements | **Feature** | **Description** | | -------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Configurable Cap for Per-Image Clusters** | You can now configure a cap on the number of clusters stored per image in MongoDB. This prevents excessive document growth for widely-deployed images and improves database performance. | | **OCI Compartment Support for Agentless Scanning** | Agentless scanning configuration now accepts OCI compartments by OCID in addition to compartment name. Use the OCID when you need to reference compartments programmatically or avoid ambiguity with duplicate names. | | **Package URL Augmentation for Binary Packages** | The scanner now augments binary packages with Package URLs (PURLs), improving software composition analysis accuracy and enabling better vulnerability correlation. | ## Security Fixes | **ISSUE** | **DESCRIPTION** | | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------ | | **Upgrade xmlquery to avoid CVE-2026-32287** | Upgraded xmlquery (and xpath) dependencies to remediate CVE-2026-32287. | | **Remove libnghttp2 from Defender Dockerfile** | Removed the libnghttp2 package from the Defender Dockerfile to eliminate a known vulnerability from the container image. | | **Updated MongoDB to 7.0.31** | Updated MongoDB from 7.0.29 to 7.0.31 to address additional security vulnerabilities. | --- # 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.prismacloud.io/ce-release-notes/prisma-tm-cloud-compute-edition-release-information/release-notes-34-04-160.md?ask=&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.