You're viewing **Apigee Edge** documentation.
[Go to the
**Apigee X** documentation](http://cloud.google.com/apigee/docs). info
On October 26, 2022, we released a new version of Apigee Edge for Private Cloud.
**Note:** This version will be supported until October 26, 2023.
> [!NOTE]
> **Note about the Apache Log4j vulnerability:**
>
>
>
> Edge for Private Cloud's default configuration contains Log4j 2 but
> is not vulnerable to Log4j 2
> ([CVE-2021-44228](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228)).
>
> Likewise, Edge for Private Cloud is not affected by the
> related vulnerability in Apache Log4j-1.x, which is shipped with ZooKeeper. That
> vulnerability requires a
> specific configuration of Log4j-1.x that Edge for Private Cloud
> does not ship as a default configuration. Therefore the vulnerability is not
> exploitable in Edge for Private Cloud.
> [!NOTE]
> For more information, see the following resources:
>
> - *[Edge for Private Cloud 4.51.00
> documentation](https://docs.apigee.com/private-cloud/v4.51.00)*
> - *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
Updating this release will update the components in the following list of RPMs:
- edge-gateway-4.51.00-0.0.60176.noarch.rpm
- edge-management-server-4.51.00-0.0.60176.noarch.rpm
- edge-message-processor-4.51.00-0.0.60176.noarch.rpm
- edge-postgres-server-4.51.00-0.0.60176.noarch.rpm
- edge-qpid-server-4.51.00-0.0.60176.noarch.rpm
- edge-router-4.51.00-0.0.60176.noarch.rpm
- edge-analytics-4.51.00-0.0.40078.noarch.rpm
- apigee-postgresql-10.17-0.0.2533.noarch.rpm
- apigee-mtls-consul-4.51.00-0.0.20160.noarch.rpm
- apigee-mtls-4.51.00-0.0.20250.noarch.rpm
- apigee-sso-4.51.00-0.0.21185.noarch.rpm
- apigee-drupal-contrib-4.51.00-0.0.409.noarch.rpm
- apigee-drupal-7.92-0.0.312.noarch.rpm
You can check the RPM versions you currently have 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 repos:
```
sudo yum clean all
```
2. Download the latest Edge 4.51.00 `bootstrap_4.51.00.sh` file to `/tmp/bootstrap_4.51.00.sh`:
```
curl https://software.apigee.com/bootstrap_4.51.00.sh -o /tmp/bootstrap_4.51.00.sh
```
3. Install the Edge 4.51.00 `apigee-service` utility and dependencies:
```
sudo bash /tmp/bootstrap_4.51.00.sh apigeeuser=uName apigeepassword=pWord
```
where uName and pWord are the username and password you received from Apigee.
If you omit pWord, 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
```
2. Update Postgres nodes (master and standby):
```
/opt/apigee/apigee-setup/bin/update.sh -c ps -f configFile
```
3. On all Edge nodes, execute the update.sh script for the edge process:
```
/opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
```
4. Execute the update.sh script for SSO on all nodes:
```
/opt/apigee/apigee-setup/bin/update.sh -c sso -f configFile
```
5. On all Apigee Developer Services portal nodes, update the devportal process by executing the following command:
```
/opt/apigee/apigee-setup/bin/update.sh -c dp -f configFile
```
6. If you are using Apigee mTLS, follow the procedure described in [Upgrade Apigee mTLS](https://docs.apigee.com/private-cloud/v4.51.00/mtls-upgrade). For more information, see [Introduction to Apigee
mTLS](https://docs.apigee.com/private-cloud/v4.51.00/mtls-intro).
## New features
This release introduces the following new feature:
### Maximum number of data centers for Apigee mTlS increased
The maximum number of data centers you can use Apigee mTLS with
has been increased to 17. (Previously it was 8.) See
[Configure multiple data centers for
Apigee mTLS](https://docs.apigee.com/private-cloud/v4.51.00/mtls-multiple).
### Support for RHEL 8.5 and 8.6
This release adds support for Red Hat Enterprise Linux (RHEL) 8.5 and 8.6.
## Security issues fixed
The following is a list of known security issues that have been fixed in this release.
To avoid these issues, install the latest version of Edge Private Cloud.
| Issue ID | Description |
|---|---|
| [CVE-2021-22569](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-22569) | Fixed a protobuf-java issue related to CVE-2021-22569. |
## Changes to
[supported software](https://docs.apigee.com/release/supported-software#apigeeedgeforprivatecloudsupportedversions)
This release adds support for Red Hat Enterprise Linux (RHEL) 8.5 and 8.6.
## Deprecations and retirements
There are no new deprecations or retirements in this release.
## Bug fixes
This section lists the Private Cloud bugs that were fixed in this release.
| Issue ID | Description |
|---|---|
| 196577907 | **BadGateway fault code was returned as a 504 Status during message processor timeout in TLS handshake** This has been fixed. |
| 238435992 | **Fixed a memory leak in the mTLS Consul component.** Previously, the mTLS Consul internal cache would not consistently autoexpire stored objects, affecting process and system stability. This has been fixed. |
| 67173662 | **Postgres upgrades were failing when more than one standby was present** This has been fixed. |
| 247003732 | **Added SQL validity checks for analytics APIs directed to aggregate tables.** Previously, checks were only being applied to fact table based analytics APIs. |
| 129865488 | **When attempting to reset the Edge login password in the UI, the **Create New Password** button was not clickable** This has been fixed. |
| 140949775 | **The Edge password reset validation pop-up in the UI was showing invalid passwords as valid** This has been fixed. |
| 140951359 | **Edge password reset validation pop-ups in the UI were overlapping** This has been fixed |
## Known issues
See [Known issues with Edge for Private Cloud](https://docs.apigee.com/release/known-issues#private-cloud)
for a complete list of known issues.