Maintained with ☕️ by
IcePanel logo

Released Apigee Edge for Private Cloud 4.53.01.03. For the list of updated RPM packages and the patch update procedure, see

Share

Services

## Announcement 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). ## Security 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). ## Fix 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. ## Announcement Announcement ### v1.17.4 On November 18, 2026 we released an updated version of the Apigee hybrid software, v1.17.4. * For information about upgrading, see[Upgrading Apigee hybrid to v1.17.4](https://cloud.google.com/apigee/docs/hybrid/v1.17/upgrade). * For information about new installations, see[The big picture](https://cloud.google.com/apigee/docs/hybrid/v1.17/big-picture). **Note:** This is a patch release. The container images used in patch releases are integrated with the Apigee hybrid Helm charts. Upgrading to a patch by using the Helm chart automatically updates the images. You don't typically need to make manual image changes. For information about container image support in Apigee hybrid releases, see[Apigee release process](https://cloud.google.com/apigee/docs/release/apigee-release-process#apigee-hybrid-container-images). ## Feature Feature **Support for Kubernetes pod topology spread constraints** In this release, you can configure Kubernetes pod topology spread constraints for Apigee hybrid runtime components (`apigeeIngressGateway`, `connectAgent`,`ingressGateways`, `istiod`, `mart`, `mcpServer`, `redis`, `redis.envoy`,`runtime`, `synchronizer`, and `watcher`) to distribute pods across availability zones and nodes (`maxSkew: 1`). You can enable and customize these constraints globally using the[topologySpreadConstraints](https://cloud.google.com/apigee/docs/hybrid/v1.17/config-prop-ref#topologyspreadconstraints)property or override them for individual runtime components using`<component>.topologySpreadConstraints` in your `overrides.yaml` file. ## Fix Fixed #### Fixed in this release | Bug ID | Description | | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **586658318** | **Security fix for Apigee.** Mitigates [CVE-2026-114938](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-114938) in the Apigee runtime, including customer-supplied Java code run by the JavaCallout policy. Customers don't need to change their callouts. | | **579213551** | **Fixed Message Processor memory leaks during proxy deployment, environment reload, and environment deletion: compiled OASValidation specifications are now shared by content hash, resources and debug session managers from superseded or failed environment loads are released, and HealthMonitorServiceImpl registrations are properly removed when unregistering health monitors.** | | **576697209** | **Fixed an issue where the LLMTokenQuota policy counted tokens for responses served from the semantic cache by the SemanticCacheLookup policy; cached responses now count as zero tokens and do not record ai\_llm\_response\_token\_count in analytics.** | | **572875915** | **Fixed an issue where the apigee-env Helm chart and Apigee operator ignored the synchronizer pollInterval configuration (synchronizer.pollInterval, envs\[\].pollInterval, and envs\[\].components.synchronizer.pollInterval); configured values now take effect, and values below 60 seconds are raised to 60.** | | **567551009** | **Added support for mutual TLS (mTLS) per environment group between the Apigee hybrid MCP data plane and apigee-ingressgateway using the virtualhosts\[\].mcpMtls configuration in the apigee-virtualhost Helm chart.** | | **565490083** | **Apigee hybrid MCP now supports the MCP 2026-07-28 stateless protocol by default and forwards OpenTelemetry trace context (traceparent, tracestate, and baggage) from a tool call's \_meta field to the backend as HTTP headers on both stateless and stateful tool calls.** | | **519116013** | **Disabled weak Diffie-Hellman (DH) TLS cipher suites on port 7070 (Prometheus jmx\_exporter) in the apigee-hybrid-cassandra container.** | | **500345401** | **The apigee-telemetry Helm chart now supports independent tolerations and nodeSelector configuration for the OpenTelemetry Collector (metrics.collector), Prometheus Adapter (metrics.adapter), and Stackdriver Exporters (metrics.proxyStackdriverExporter and metrics.appStackdriverExporter).** | | **263483775** | **Added support for configuring Kubernetes [topologySpreadConstraints](https://cloud.google.com/apigee/docs/hybrid/v1.17/config-prop-ref#topologyspreadconstraints) globally (topologySpreadConstraints) and per component (<component>.topologySpreadConstraints) for Apigee hybrid runtime-pool workloads.** | ## Security Security | Bug ID | Description | | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **N/A** | **Security fixes for apigee-asm-ingress.** This addresses the following vulnerabilities: [CVE-2026-116587](https://nvd.nist.gov/vuln/detail/CVE-2026-116587) [CVE-2026-5450](https://nvd.nist.gov/vuln/detail/CVE-2026-5450) [CVE-2026-5928](https://nvd.nist.gov/vuln/detail/CVE-2026-5928) | | **N/A** | **Security fixes for apigee-asm-istiod.** This addresses the following vulnerabilities: [CVE-2026-116587](https://nvd.nist.gov/vuln/detail/CVE-2026-116587) [CVE-2026-5450](https://nvd.nist.gov/vuln/detail/CVE-2026-5450) [CVE-2026-5928](https://nvd.nist.gov/vuln/detail/CVE-2026-5928) | | **N/A** | **Security fixes for apigee-fluent-bit.** This addresses the following vulnerabilities: [CVE-2026-111497](https://nvd.nist.gov/vuln/detail/CVE-2026-111497) [CVE-2026-27171](https://nvd.nist.gov/vuln/detail/CVE-2026-27171) [CVE-2026-76844](https://nvd.nist.gov/vuln/detail/CVE-2026-76844) [CVE-2026-85091](https://nvd.nist.gov/vuln/detail/CVE-2026-85091) | | **N/A** | **Security fixes for apigee-hybrid-cassandra.** This addresses the following vulnerabilities: [CVE-2026-19032](https://nvd.nist.gov/vuln/detail/CVE-2026-19032) [CVE-2026-49844](https://nvd.nist.gov/vuln/detail/CVE-2026-49844) [CVE-2026-68497](https://nvd.nist.gov/vuln/detail/CVE-2026-68497) [CVE-2026-83557](https://nvd.nist.gov/vuln/detail/CVE-2026-83557) [CVE-2026-89407](https://nvd.nist.gov/vuln/detail/CVE-2026-89407) [CVE-2026-89425](https://nvd.nist.gov/vuln/detail/CVE-2026-89425) [CVE-2026-91776](https://nvd.nist.gov/vuln/detail/CVE-2026-91776) [CVE-2026-91777](https://nvd.nist.gov/vuln/detail/CVE-2026-91777) | | **N/A** | **Security fixes for apigee-hybrid-cassandra-client.** This addresses the following vulnerabilities: [CVE-2026-116585](https://nvd.nist.gov/vuln/detail/CVE-2026-116585) [CVE-2026-116586](https://nvd.nist.gov/vuln/detail/CVE-2026-116586) [CVE-2026-116587](https://nvd.nist.gov/vuln/detail/CVE-2026-116587) | | **N/A** | **Security fixes for apigee-open-telemetry-collector.** This addresses the following vulnerability: [CVE-2026-116587](https://nvd.nist.gov/vuln/detail/CVE-2026-116587) | | **N/A** | **Security fixes for apigee-watcher.** This addresses the following vulnerabilities: [CVE-2026-116585](https://nvd.nist.gov/vuln/detail/CVE-2026-116585) [CVE-2026-116586](https://nvd.nist.gov/vuln/detail/CVE-2026-116586) [CVE-2026-116587](https://nvd.nist.gov/vuln/detail/CVE-2026-116587) |