You're viewing **Apigee Edge** documentation.  
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info

On April 28, 2025, we released a new version of Apigee Edge for Private Cloud.

> [!NOTE]
> For more information, see the following resources:
>
> - *[Edge for Private Cloud 4.52.02 documentation](https://docs.apigee.com/private-cloud/v4.52.02)*
> - *Questions or issues?* Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support)
> - *[Edge for Private Cloud support timeline](https://docs.apigee.com/release/apigee-edge-release-process#apigee-edge-for-private-cloud-support-timeline)*
> - *Release notifications* : See [Get Apigee Edge release notifications](https://docs.apigee.com/release/get-release-notifications)

## Update procedure

This section describes how to install this release if you are updating from the previous
release of Edge for Private Cloud. If you need to update from an earlier release, see
[Applying Multiple Patch Versions](https://docs.apigee.com/release/notes/4520203-edge-private-cloud-release-notes#applying-multiple-patch-versions).

Updating this release will update the components listed below:

- edge-gateway-4.52.02-0.0.60277.noarch.rpm
- edge-management-server-4.52.02-0.0.60277.noarch.rpm
- edge-message-processor-4.52.02-0.0.60277.noarch.rpm
- edge-postgres-server-4.52.02-0.0.60277.noarch.rpm
- edge-qpid-server-4.52.02-0.0.60277.noarch.rpm
- edge-router-4.52.02-0.0.60277.noarch.rpm
- edge-ui-4.52.02-0.0.20265.noarch.rpm
- edge-management-ui-4.52.02-0.0.20039.noarch.rpm

You can check the RPM versions currently installed to see if they
need to be updated by entering:

```
apigee-all version
```

To update your installation, perform the following procedure on the Edge nodes:

1. On all Edge nodes:

   1. Clean the Yum repositories:

      ```
      sudo yum clean all
      ```
   2. Download the latest Edge 4.52.02 `bootstrap_4.52.02.sh` file to `/tmp/bootstrap_4.52.02.sh`:

      ```
      curl https://software.apigee.com/bootstrap_4.52.02.sh -o /tmp/bootstrap_4.52.02.sh
      ```
   3. Install the Edge 4.52.02 `apigee-service` utility and dependencies:

      ```
      sudo bash /tmp/bootstrap_4.52.02.sh apigeeuser=uName apigeepassword=pWord
      ```

      Where <var translate="no">uName</var> and <var translate="no">pWord</var> are the username and password you received from Apigee. If you omit <var translate="no">pWord</var>, you will be prompted to enter it.
   4. Use the `source` command to execute the `apigee-service.sh` script:

      ```
      source /etc/profile.d/apigee-service.sh
      ```
   5. Update the `apigee-setup` utility:

      ```
      apigee-service apigee-setup update
      ```
2. On all Edge nodes, execute the `update.sh` script for the `edge` process (including monetization):

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
   ```
3. On all UI nodes, execute the `update.sh` script for the UI:

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c ui -f configFile
   ```
4. If you are using the New Edge experience, execute the following command:

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c ue -f configFile
   ```

## Bug fixes

This section lists the Private Cloud bugs that were fixed in this release.

| Issue ID | Description |
|---|---|
| 391319737 | Fixed a bug in the `configure-sso` script that impacted the UI. |
| 319447467 | Enhanced security by applying additional restrictions to Python scripts used in the `PythonScript` policy when the security manager is enabled. |
| 382967738 | The `JavaCallout` policy now includes additional security measures during Java class instantiation. These enhancements prevent the deployment of policies that directly or indirectly attempt actions that require disallowed permissions. In most cases, existing policies will continue to function as expected without any issues. However, policies that rely on third-party libraries or contain custom code that indirectly triggers operations requiring elevated permissions may be affected. **Note:** These additional security restrictions take effect only when the Security Manager is enabled. For more details about the Java Security Manager, refer to the [Java permissions reference](https://docs.apigee.com/api-platform/reference/java-permission-reference). |

## Security issues fixed

This section lists the Private Cloud security issues that were fixed in this release.

| Issue ID | Description |
|---|---|
| 443902061 | Security fix for Apigee infrastructure. This addresses the following vulnerability: - CVE-2025-13292Fixed an issue with improper access control that resulted in cross-tenant analytics modification and access to log data. <br /> |

## Changes to supported software

No support for new software has been included in this release.

## Deprecations and retirements

There are no new deprecations or retirements in this release.

## New features

There are no new features in this release.

## Known issues

See [Known issues with Edge for Private Cloud](https://docs.apigee.com/release/known-issues#private-cloud-known-issues)
for a complete list of known issues.

## Applying multiple patch versions

This section describes how to apply multiple patch versions, in case you are updating from
a version of Edge for Private Cloud that is earlier than the previous patch release version.

Each patch release contains updates to specific components of Edge for Private Cloud, such as
`edge-management-server`.
To apply multiple patch versions, you need to update each Edge component that was included in
a patch release later than your currently installed version. You can find these components by
looking at the Edge for Private Cloud release notes for all versions later than your current
version, and checking the list of RPMs for those releases. See
[Apigee Release Notes](https://docs.apigee.com/release/notes/apigee-release-notes) for links to all
Edge for Private Cloud release notes.

**Note:** You only need to update each component once, by installing the RPM for the latest
version of the component included in the patch releases. Follow the instructions in the
release notes for that version to update the component.

**Note:** Upgrading a component automatically installs the latest patch version of a
component. If you want to upgrade to a patch version that is not the latest, you need to
maintain your own
tarball copy of Apigee's repo using Apigee mirror, and use this mirror for Apigee installations.
For more information, refer to [Using a local Edge repository to maintain your Edge version](https://docs.apigee.com/private-cloud/v4.52.02/installation-overview#local-repo).