> 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/34.05-build-34.05.157.md).
# 34.05 (Build 34.05.157)
The following table has the release details:
| Build | 34.05.157 |
| ------------ | ---------------------------------------------------------------- |
| Code name | Quinn Update 5 |
| Release date | August 2, 2026 |
| Type | Major release |
| SHA-256 | 753cd98c5a19ca5dea73cab261bbf8a17688df7426a190e6d755f1f6760fa277 |
## 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`.
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.
* [Enhancements](#enhancements)
* [Changes in behavior](#changes-in-existing-behavior)
## Enhancements
| **Enhancement** | **Details** |
| --------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Support for Rocky Linux 10.x (Red Quartz)** | Prisma Cloud Compute now supports Rocky Linux 10.x (Red Quartz) for vulnerability and compliance scanning and for runtime protection. |
| **Rocky Linux — source-package and epoch support** | During scanning, Rocky Linux binary packages are now linked to their source package (for example, `expat-devel` and `expat-libs` linked to `expat`). This ensures that CVE matches against the Rocky Linux errata feed are no longer missed. Version comparison also honors the RPM epoch, which eliminates a class of false positives on Rocky Linux images. |
| **Support for RKE2 v1.35** | Defenders now deploy successfully on RKE2 v1.35 clusters. Previously, defenders failed to connect to Console because CRI-client initialization could not determine the container runtime version on newer RKE2 releases. |
| **Host defender support on RHEL 10 with nftables** | Host defenders deployed on RHEL 10 with the `-n` (nftables) install flag no longer log spurious `iptables: executable file not found in $PATH` errors while evaluating the Linux CIS firewall configuration. |
| **Generic distro-based CVE exclusion via custom feed entries** | Custom CVE exclusions now support any OS distribution — Windows, Ubuntu, Red Hat, Alpine, and others — extending the existing PAN-OS / GKE mechanism. Administrators can upload custom `excludedCve` entries per target distribution through the portal to suppress specific CVEs from vulnerability results. |
| **False-positive suppression for CVEs on OpenShift nodes** | OpenShift node scans now filter out CVEs that Red Hat has marked as "not affected" for the OpenShift version in the VEX feed. This eliminates false positives such as `CVE-2025-30204` on OpenShift 4.14 RHCOS nodes. |
| **Environment variables printed on defender startup** | On startup, the defender now logs all of its environment variables, making support cases involving env-var configuration significantly faster to triage. |
| **Defender image — Red Hat Ecosystem Catalog certification** | The defender image now includes the required labels (`name`, `vendor`, `version`, `release`, `summary`, `description`, `maintainer`) and a `/licenses` folder with license files (MIT, Apache, and others), enabling certification in the Red Hat Ecosystem Catalog. |
| **Agentless OCI — compartment ID support** | The Agentless scanner for Oracle Cloud Infrastructure now supports specifying a compartment ID, which allows customers to scope agentless scans to a specific OCI compartment. |
| **Agentless AWS — expanded fallback instance types** | The Agentless scanner now uses additional fallback instance types beyond `m5.2xlarge`, `m4.2xlarge`, `m3.2xlarge`, `t2.2xlarge`, and `m6i.2xlarge`. This allows agentless scans to succeed in AWS regions where the current defaults are unavailable (for example, `af-south-1`, `me-central-1`, `il-central-1`, `ap-southeast-4`, `eu-central-2`, and others). |
| **Registry scan — image deduplication by digest** | Registry scans configured with a Cap now deduplicate images by digest before enforcing the Cap, so the same image referenced by multiple tags is no longer scanned repeatedly or double-counted against the Cap. |
| **Vulnerability / Compliance Explorer — daily refresh at very large scale** | The daily compliance-stats aggregation in `db.AggregatedComplianceData` is restructured so it no longer accumulates a `$push` array that exceeds MongoDB's hard-coded 100 MiB internal limit. This unblocks daily refresh of the Vulnerability and Compliance Explorer for very large tenants (\~4M+ container compliance hits). A workaround is also available: set the new `MONGO_DB_CUSTOM_CONFIG_PATH` environment variable to mount a custom mongodb configuration that raises `internalQueryMaxPushBytes` from 100 MiB to 500 MiB. |
| **LDAP users in multiple groups — access to all assigned collections** | On on-prem consoles using LDAP, when a user belongs to multiple LDAP groups mapped to custom roles, the user is now granted access to every collection associated with those groups instead of only the first collection. |
## Changes in Behavior
| **Feature** | **Description** |
| ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Removal of environment-variable printing from defender failure log** | The defender no longer prints its environment variables to the log on failure. This complements the new startup-time env-var dump (see Enhancements) and prevents environment state from appearing in failure logs. |
---
# 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/34.05-build-34.05.157.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.