> 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-156.md). # 34.04 (Build 34.04.156) The following table has the release details: | Build | 34.04.156 | | ------------ | ---------------------------------------------------------------- | | Code name | Quinn Update 4 | | Release date | March 29, 2026 | | Type | Minor release | | SHA-256 | 9099536097666d5bce8108135c0bf04857f9c0f5f94412c275faefb0a560e0f8 | 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** | | ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Restrict UI access for access key logins** | Added ability to block login using an access key via the CWP login UI page under a feature flag, aligning with the way access key based logins are handled by the main Prisma login page. | | **FIPS configuration via environment variable** | Added support for setting the `FIPS_ENABLED` configuration from an environment variable in `twistlock.cfg`. | | **nginx\_unit vulnerability detection** | Added vulnerability detection support for nginx\_unit application server binaries. | ## Security Fixes | **ISSUE ID** | **DESCRIPTION** | | ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Suppressed CVE-2026-33186 in gRPC** | Suppressed CVE-2026-33186 in the gRPC vendor dependency via database migration. This supression was added because the vulnerability is not applicable to our use of gRPC. Specifically, the vulnerability is related to path-based authorization, and the authorization bypass described in CVE-2026-33186 does not impact the application. We do not use the `grpc/authz` package or implement custom path-based authorization on our gRPC servers. | | **Updated goxmldsig library** | Updated the goxmldsig SAML XML signature library to address security vulnerabilities. | | **Upgraded Jackson to 2.18.6** | Upgraded Jackson dependency to 2.18.6 to address GHSA-72hv-8253-57qq. | | **Updated MongoDB to 7.0.29** | Updated MongoDB from 7.0.28 to 7.0.29 to address 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 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://docs.prismacloud.io/ce-release-notes/prisma-tm-cloud-compute-edition-release-information/release-notes-34-04-156.md?ask=&goal= ``` `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.