This page documents releases and patches for Apigee Edge for Private Cloud.
We recommend that users periodically check this list for
any new announcements, or [subscribe](https://docs.cloud.google.com/apigee/docs/edge-private-cloud/release-notes.md.txt#sub) to this page using a
feed reader to get notifications of updates.
<button class="devsite-dialog-button button-white button-unindented" data-modal-dialog-id="feed-reader-modal-dialog">What is a feed reader?</button>

### What is a feed reader?

Really simple syndication (RSS) feed readers aggregate content from
websites that you specify.

Feed reader notifications can be email-, browser-, desktop-, or
mobile-based. Some readers are free, or have free versions, and some
require a subscription.

A few examples:

- [Feedly](https://feedly.com)
- [Feedreader](https://feedreader.com)
- [Feeder](https://feeder.co/)

More information on RSS:

- [RSS](https://en.wikipedia.org/wiki/RSS)
- [Comparison of feed aggregators](https://en.wikipedia.org/wiki/Comparison_of_feed_aggregators)
<button class="devsite-dialog-close">Close</button>

<br />

See also:

- [Release notes published before September 2026](https://docs.apigee.com/release/notes/apigee-release-notes)
- [Apigee Edge for Public Cloud release notes](https://docs.cloud.google.com/apigee/docs/edge-public-cloud/release-notes.md.txt)
- [Known issues with Edge for Private Cloud](https://docs.apigee.com/release/known-issues#private-cloud-known-issues)


Subscribe:

To get the latest product updates delivered to you, add the URL of this page to your
[feed
reader](https://wikipedia.org/wiki/Comparison_of_feed_aggregators), or add the
[feed URL](https://docs.cloud.google.com/feeds/apigee-edge-private-cloud-release-notes.xml) directly.

## November 18, 2026

4.53.01.03 Announcement Released Apigee Edge for Private Cloud 4.53.01.03.

For the list of updated RPM packages and the patch update procedure, see
[4.53.01.03 - Edge for Private Cloud release notes](https://docs.apigee.com/release/notes/4530103-edge-private-cloud-release-notes#updateprocedure).
4.53.01.03 Security Fixed multiple security vulnerabilities in Apigee Edge for Private Cloud,
including security hardening across Edge runtime, management, New Edge UI,
and Apigee mTLS components.

Changed the `bcfks-cacerts` file shipped with `edge-gateway` to an empty BCFKS
store, and Apigee mTLS now rejects SHA-1-signed custom certificates. Before you
update, move to your own BCFKS keystore and truststore at a different path on
FIPS-enabled systems that use the default store, and re-sign custom mTLS
certificates with SHA-256. See the
[update procedure](https://docs.apigee.com/release/notes/4530103-edge-private-cloud-release-notes#updateprocedure).
4.53.01.03 Fixed Resolved the following issues in Apigee Edge for Private Cloud 4.53.01.03:

- Fixed an issue where API proxy deployments that use the `OASValidation` policy failed with OpenAPI Specification path parameter validation errors after updating to 4.53.01.
- Fixed an issue where running `setup.sh -p uapim` failed during `edge-uapim-connector` setup.
- Added sanitization to certain error messages generated by Message Processors.

## November 09, 2026

4.54.00.01 Announcement Released Apigee Edge for Private Cloud 4.54.00.01.

For the list of updated RPM packages and the patch update procedure, see
[Install 4.54.00.x patch updates](https://docs.apigee.com/private-cloud/v4.54.00/update-apigee-edge-45400-patch#4540001).
4.54.00.01 Security Fixed multiple security vulnerabilities in Apigee Edge for Private Cloud,
including security hardening across Edge runtime, management, New Edge UI,
OpenLDAP, Apigee mTLS, and Nginx components.
4.54.00.01 Fixed Resolved the following issues in Apigee Edge for Private Cloud 4.54.00.01:

- Fixed an issue in the New Edge UI where creating an OpenAPI Specification in the `OASValidation` policy modal stored the specification resource under `yaml://` or `json://` instead of `oas://`.
- Fixed an issue where running `setup.sh -p uapim` failed during `edge-uapim-connector` setup.
- Apigee Edge for Private Cloud 4.54.00 and its patch releases support Red Hat Enterprise Linux, Oracle Linux, and Rocky Linux 8.10, 9.6, 9.7, and 9.8. See [Supported software and supported versions](https://docs.apigee.com/release/supported-software#apigeeedgeforprivatecloudsupportedversions).

## October 15, 2026

4.54.00 Announcement Released Apigee Edge for Private Cloud 4.54.00.

Designated Apigee Edge for Private Cloud 4.54.00.00 a long-term support (LTS)
release: 18 months of full support ending April 2028, then 18 months of
maintenance ending October 2029. After October 2029, 4.54.00.00 receives no
software updates, security mitigations, or technical support.

Installing a later 4.54 minor release or patch does not change those dates. To
extend the support lifecycle, upgrade to the next LTS release.

For the support lifecycle phases, release cadences, and version numbering, see
[Apigee Edge for Private Cloud release and lifecycle policy](https://docs.apigee.com/release/private-cloud-release-lifecycle-policy).
4.54.00 Announcement This release replaces Java 8 with Java 17 and Java 21, removes the Classic UI
and the `apigee-sso` component, and updates the bundled Cassandra, Postgres,
OpenLDAP, ZooKeeper, Qpid Broker-J, Nginx, and Consul versions. These changes
are not backward-compatible.

For the 4.54.00 versions and the 4.53.01 versions they replace, see
[Supported software and supported versions](https://docs.apigee.com/release/supported-software).

Before upgrading, read
[Changes in Edge for Private Cloud 4.54.00](https://docs.apigee.com/private-cloud/v4.54.00/changes-privatecloud-45400),
then
[Update Apigee Edge 4.53.00 or 4.53.01 to 4.54.00](https://docs.apigee.com/private-cloud/v4.54.00/update-apigee-edge-4530x-45400)
or
[New installation overview](https://docs.apigee.com/private-cloud/v4.54.00/installation-overview).
For known issues, see
[Known issues with Edge for Private Cloud](https://docs.apigee.com/release/known-issues#private-cloud-known-issues).
4.54.00 Announcement Replaced the Classic UI (`edge-ui`) with the
[New Edge UI](https://docs.apigee.com/private-cloud/v4.54.00/new-edge-ui)
(`edge-management-ui`).

The New Edge UI is the only management UI in 4.54.00 and is installed by
default. Deployments running the Classic UI must transition to it before
upgrading. Custom Classic UI properties do not carry over automatically. The
default port also changes from `9000` to `3001`, configurable with
`conf_uebe_port`, so firewall rules and load balancer target ports that point
at `9000` fail until they are updated.

For the migration steps and the supported feature list, see
[Migrate to the New Edge UI](https://docs.apigee.com/private-cloud/v4.54.00/migrate-ui)
and
[What features are supported?](https://docs.apigee.com/private-cloud/v4.54.00/new-edge-ui#features).
4.54.00 Breaking In deployments with Apigee SSO enabled, an integrated OIDC identity broker in
`apigee-openldap` replaces the standalone `apigee-sso` component and Apache
Tomcat 9.0.x. Before upgrading, take a complete and validated LDAP backup;
existing `apigee-sso` configurations do not migrate automatically. Deployments
not using Apigee SSO require no action.

For migration prerequisites, validation checks, and rollback constraints, see
[Option 2: Upgrade UI (with Apigee SSO)](https://docs.apigee.com/private-cloud/v4.54.00/update-apigee-edge-4530x-45400#upgrade-ui-with-apigee-sso).
4.54.00 Breaking 4.54.00 runs Java in mixed mode: Java 17 for Cassandra and ZooKeeper, Java 21
for the Management Server, Message Processor, Router, and Qpid Broker-J. Both
Oracle JDK and OpenJDK are supported at those versions.

Oracle JDK 8 and OpenJDK 8 are no longer supported.

API proxies with custom JavaCallout policies or custom resource JARs can break
on Java 21. For details, see
[Changes in Edge for Private Cloud 4.54.00](https://docs.apigee.com/private-cloud/v4.54.00/changes-privatecloud-45400).
4.54.00 Change Upgraded Nginx on the Edge Router to 1.30.0.

If you are upgrading from Nginx 1.20.x, see
[Nginx 1.30 changes in Apigee Edge 4.54.00](https://docs.apigee.com/private-cloud/v4.54.00/nginx-45400)
for the full list of changes.
4.54.00 Change Changed the TLS defaults on Message Processors to the Java 21 cryptographic
baseline.

Message Processors run on Java 21, which enables TLS 1.3 by default
([JEP 332](https://openjdk.org/jeps/332)) and prefers it for outbound backend
connections, falling back to TLS 1.2. No configuration change is required if
your target servers and load balancers negotiate TLS 1.3, or negotiate TLS 1.2
with forward-secret (ECDHE) cipher suites.

Java 21 also disables the non-forward-secret static RSA key-exchange suites
(`TLS_RSA_*`). If you have overridden
`conf_http_HTTPTransport.ssl.cipher.suites.whitelist` or
`conf_message-processor-communication_local.http.ssl.ciphers` with static RSA
suites only, backend calls fail with `no cipher suites in common` and the
Router cannot complete a TLS handshake with the Message Processor. Replace the
`TLS_RSA_*` entries with modern cipher suites and restart the Message
Processor.

For the remediation path, see
[Legacy backend requirements and remediation](https://docs.apigee.com/private-cloud/v4.54.00/changes-privatecloud-45400#legacy-tls-remediation).
4.54.00 Feature Added Basic authentication to the New Edge UI, which lets you sign in without
configuring an identity provider.

The [New Edge UI](https://docs.apigee.com/private-cloud/v4.54.00/new-edge-ui)
supports Basic authentication without additional configuration. You can also
configure Apigee SSO, or an external identity provider such as SAML or OIDC.
This feature is generally available in 4.54.00.
4.54.00 Feature Added automated pre-flight validation checks to `apigee-setup` and
`apigee-service`, which surface environment configuration problems before a
component is installed.

This feature is generally available in 4.54.00.
4.54.00 Security Fixed multiple security vulnerabilities in Apigee Edge for Private Cloud
4.54.00.

These fixes ship as part of the component upgrades in this release; see
[Changes in Edge for Private Cloud 4.54.00](https://docs.apigee.com/private-cloud/v4.54.00/changes-privatecloud-45400).
4.54.00 Change Changed the default garbage collector on Message Processors to the
Garbage-First garbage collector.

Message Processors set `useG1GC=true` and `useStringDeduplication=true` by
default in 4.54.00. In 4.53.01 neither was set by default. To configure garbage
collection, see
[Configure the garbage collector for Message Processors](https://docs.apigee.com/private-cloud/v4.54.00/configuring-gc-message-processors-4.54).

## September 02, 2026

Announcement Apigee Edge for Private Cloud release notes are now published on Google Cloud
documentation.

Release notes and patch announcements for Apigee Edge for Private Cloud are
published on the
[Apigee Edge for Private Cloud release notes](https://docs.cloud.google.com/apigee/docs/edge-private-cloud/release-notes.md.txt)
page from September 2026 onward. You can
[subscribe](https://docs.cloud.google.com/apigee/docs/edge-private-cloud/release-notes.md.txt#sub) to that page with
a feed reader to be notified when a new release or patch is published.

Release notes published before September 2026 remain available in the
[Apigee Edge release notes archive](https://docs.apigee.com/release/notes/apigee-release-notes).