This page documents production updates to Apigee Edge for Public Cloud, including updates to the Edge UI, SSO, Message Processor, and the integrated portal. This page also documents Edge Microgateway releases, starting with version 3.3.12. We recommend that users periodically check this list for any new announcements, or subscribe to this page using a feed reader to get notifications of updates.
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:
More information on RSS:
See also:
To get the latest product updates delivered to you, add the URL of this page to your feed reader, or add the feed URL directly.
November 05, 2026
Scheduled maintenance of Management/Control Plane for the Apigee Edge for Public Cloud on November 6, 2026.
Scheduled maintenance of Management/Control Plane for the Apigee Edge for Public Cloud production will take place on Friday, November 6, 2026, from 9:00 PM PT to 10:00 PM PT (Saturday, November 7, 2026, from 5:00 AM UTC to 6:00 AM UTC). This maintenance follows the monthly maintenance window schedule documented in the Apigee Edge release notes archive.
During the scheduled maintenance window, the following services will be
temporarily unavailable, and attempts to access them will return a 4xx status
code:
- Management Services UI
- Management Services APIs
- Monetization Management APIs
- New proxy deployments
- DevPortal Service
- Microgateway Services
- Edge Query (Analytics Stats APIs)
Runtime API calls to deployed API proxies are unaffected. While access to analytics queries may be temporarily unavailable during the maintenance window, all analytics and metrics data from this period will be available once maintenance ends.
November 04, 2026
Released Edge Microgateway 3.3.12.
Edge Microgateway 3.3.12 includes the following component versions:
| Component | Version |
|---|---|
| microgateway | 3.3.12 |
| plugins | 3.3.9 |
| edgeauth | 3.2.2 |
To upgrade, install version 3.3.12 of the edgemicro npm package or pull the
gcr.io/apigee-microgateway/edgemicro:3.3.12 Docker image. For the npm upgrade
steps, see
Upgrading Edge Microgateway.
For earlier Edge Microgateway releases, see
Edge Microgateway release notes.
Removed support for Node.js 20 from Edge Microgateway. Use Node.js 22, 24, or 26 instead.
Edge Microgateway 3.3.12 supports only Node.js 22, 24, and 26. Support for Node.js 26 is new in this release. Before you upgrade an npm installation of Edge Microgateway to 3.3.12, upgrade the Node.js runtime on each host to version 22, 24, or 26. The 3.3.12 Docker image is built on Node.js 24, so Docker deployments need no action for this change. For supported versions, see Supported software and supported versions.
Removed the npm and npx command-line tools from the Edge Microgateway Docker
image. Install custom plugin dependencies before you add the plugins to the
container.
Starting with version 3.3.12, the Edge Microgateway Docker image doesn't include
npm or npx, and commands that run either tool inside the container fail. The
change doesn't affect how Edge Microgateway runs. If your custom plugins have
npm dependencies, run npm install in each plugin directory before you add the
plugins to the container, so that each plugin's node_modules directory is
included. For the steps, see
Adding a custom plugin.
This change doesn't affect npm installations of Edge Microgateway.
Fixed multiple security vulnerabilities in Edge Microgateway. Upgrade to Edge Microgateway 3.3.12.
Edge Microgateway 3.3.12 fixes the following vulnerabilities:
- CVE-2026-12590
- CVE-2026-14257
- CVE-2026-45819
- CVE-2026-54272
- CVE-2026-59870
- CVE-2026-69152
- CVE-2026-69192
- CVE-2026-69198
- CVE-2026-73088
- CVE-2026-73089
- CVE-2026-82417
- CVE-2026-82562
- CVE-2026-84375
- CVE-2026-87018
- CVE-2026-101910
- CVE-2026-101911
- CVE-2026-101912
- CVE-2026-101913
- CVE-2026-102276
- CVE-2026-102277
- CVE-2026-102278
- CVE-2026-109383
- CVE-2026-109869
- CVE-2026-109924
- CVE-2026-109932
- CVE-2026-110816
- CVE-2026-111181
- CVE-2026-111497
- CVE-2026-111997
- CVE-2026-115897
The Edge Microgateway 3.3.12 Docker image is built on
node:24.22.1-trixie-slim, which includes the Node.js fix for CVE-2026-111497.
For npm installations of Edge Microgateway, upgrading the edgemicro package
doesn't fix CVE-2026-111497. You must also upgrade the Node.js runtime on each
host to one of the following versions, or to a later version in the same
release line:
| Node.js release line | Fixed version |
|---|---|
| 22.x | 22.23.4 |
| 24.x | 24.22.1 |
| 26.x | 26.12.1 |
October 15, 2026
On October 15, 2026, we began releasing Single Sign-On (SSO) updates for Apigee Edge for Public Cloud.
| Bug ID | Component | Description |
|---|---|---|
| 560310696 | SSO | Fixed an issue where the Portal SSO endpoint inadvertently accepted deprecated TLS 1.1 connections. The endpoint now strictly enforces TLS 1.2+. |
October 05, 2026
Security fixes for the integrated portal and API specs in the Apigee Edge management UIs.
The Apigee Edge UIs for managing integrated portals and API specs were updated to patch vulnerabilities in underlying libraries and serving components. Functionality is unchanged, but some pages might show minor styling differences.
September 02, 2026
Apigee Edge for Public Cloud release notes are now published on Google Cloud documentation.
Release notes for Apigee Edge for Public Cloud, including its Edge UI, SSO, Message Processor, and integrated portal components, are published on the Apigee Edge for Public Cloud release notes page from September 2026 onward. You can subscribe to that page with a feed reader to be notified when a new release is published.
Release notes published before September 2026 remain available in the Apigee Edge release notes archive.