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

On February 19, 2021, we released a new version of Apigee Edge for Private Cloud.

> [!NOTE]
> For more information, see the following resources:
>
> - *[Edge for Private Cloud 4.19.06
>   documentation](https://docs.apigee.com/private-cloud/v4.19.06)*
> - *Questions or issues?* Contact [Apigee Edge Support](https://docs.apigee.com/api-platform/troubleshoot/support)
> - *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-analytics-4.19.06-0.0.40038.noarch.rpm
- apigee-tomcat-7.0.105-0.0.911.noarch.rpm
- apigee-sso-4.19.06-0.0.20134.noarch.rpm
- edge-gateway-4.19.06-0.0.20112.noarch.rpm
- edge-management-server-4.19.06-0.0.20112.noarch.rpm
- edge-message-processor-4.19.06-0.0.20112.noarch.rpm
- edge-postgres-server-4.19.06-0.0.20112.noarch.rpm
- edge-qpid-server-4.19.06-0.0.20112.noarch.rpm
- edge-router-4.19.06-0.0.20112.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.19.06 `bootstrap_4.19.06.sh` file to `/tmp/bootstrap_4.19.06.sh`:

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

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

      where <var translate="no">uName: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. Update the `apigee-setup` utility:

      ```
      sudo /opt/apigee/apigee-service/bin/apigee-service apigee-setup update
      ```
   5. Use the `source` command to execute the `apigee-service.sh` script:

      ```
      source /etc/profile.d/apigee-service.sh
      ```
2. On all Edge nodes, execute the `update.sh` script for the `edge` process. To do this, execute the following command on each node:

   ```
   /opt/apigee/apigee-setup/bin/update.sh -c edge -f configFile
   ```
3. Execute the `update.sh` script for SSO on all nodes. On each node, execute the following command:

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

## Changes to
[supported software](https://docs.apigee.com/release/supported-software#apigeeedgeforprivatecloudsupportedversions)

Tomcat has been upgraded to version 7.0.105 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.

## Bugs fixed

The following table lists the bugs fixed in this release:

| Issue ID | Description |
|---|---|
| 166766984 | **Apache Tomcat was upgraded to version 7.0.105.** |
| 165843063 | **Management server was listening on the wrong port (8080) in response to the `wait_for_ready` command.** |
| 139051927 | **API proxies were experiencing high request processing latencies.** |
| 172587165 | **Custom variables were occasionally not showing up in UI reports.** This process has been improved and made more robust. |
| 174241354 | **Empty messages to the MessageLogging policy were causing it to flood logs with warnings.** Empty messages are now handled correctly. |
| 168258482 | **Some incorrect directory permissions in `apigee-tomcat` were causing `apigee-service` commands to fail.** |
| 161858295 | **Some silent config variables were misspelled.** The silent config variable `SSO_JWT_SIGNING_KEY_FILEPATH` is now spelled correctly. |
| 157521855 | **Configuring cipher suites when enabling TLS for Management API was not working correctly.** |

## 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-2020-13935](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13935) | The payload length in a WebSocket frame was not correctly validated. Invalid payload lengths could trigger an infinite loop. Multiple requests with invalid payload lengths could lead to a denial of service. Affected Versions: Apache Tomcat 10.0.0-M1 to 10.0.0-M6, Apache Tomcat 9.0.0.M1 to 9.0.36, Apache Tomcat 8.5.0 to 8.5.56, and Apache Tomcat 7.0.27 to 7.0.104. |
| 178784031 | **Assertions that are used to validate HTTP responses were not being signed by default, leading to a potential security issue.** Assertions are now signed by default. |

## Known issues


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