The following describes security bulletins related to Apigee.
To get the latest security bulletins delivered to you, do one of the following:
- Add the URL of this page to your feed reader.
- Add the feed URL directly to your feed reader:
https://cloud.google.com/feeds/apigee-security-bulletins.xml
GCP-2026-077
Published: 2026-11-03
Description
| Description | Severity | Notes | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Following the private-key compromise of intermediate Certificate Authorities (CAs) associated with eMudhra (emSign), outbound TLS connections trusting affected roots—specifically Impact of remediationMoving forward, outbound connections to endpoints using certificates signed by compromised roots will be blocked unless a custom trust store is configured in your outbound setup. Disruption of outbound connectivity resulting from the security revocation of compromised third-party certificates or customer trust store configurations does not constitute Google Cloud service downtime under applicable Service Level Agreements (SLAs). Affected products and versions
What should I do?Important: The remediation steps and commands provided herein are for guidance purposes only. Customers are solely responsible for testing modifications in a non-production environment and taking complete backups of keystores, trust stores, and system configurations prior to execution. Google provides these instructions "as-is" without warranty of any kind. Apigee XGoogle Cloud is conducting a rollout across Apigee X infrastructure to remediate affected trust stores and Go toolchains. Customer Action Required: Automated platform rollout handles control plane and runtime containers. Customers must review custom TrustStores in TargetEndpoint or TargetServer configurations to ensure compromised emSign or AAA Certificate Services certificates are not explicitly trusted. To verify trust store compliance, see Apigee X/Hybrid: Review and Update Custom TrustStores (eMudhra CA Compromise). Apigee HybridApigee Hybrid containers do not bind-mount host OS certificate stores and use isolated trust stores baked into image builds; customers must upgrade to patched container images once released:
Apigee Edge (SaaS)Google Cloud is applying automated platform updates across all Apigee Edge infrastructure to remove compromised eMudhra and AAA Certificate Services root and intermediate certificates from system keystores. Customer Action Required: Automated platform rollout handles system trust stores. Customers must review custom TrustStores in TargetEndpoint or TargetServer settings to ensure compromised emSign or AAA Certificate Services certificates are not explicitly trusted. To review or create trust stores, see Creating keystores and truststores using the Edge UI. Apigee Edge for Private Cloud (OPDK)Customers hosting Apigee Edge on-premises or in private cloud infrastructure (OPDK) must update their system environment, sanitize Java keystores, and perform a host/service reload across all cluster nodes. Phase 1: Update the Host OS CA Certificate StoreFor Red Hat Enterprise Linux / CentOS / Rocky Linux: sudo yum update -y ca-certificates sudo update-ca-trust extract Phase 2: Sanitize FIPS JVM TrustStores1. If you're FIPS-enabled and still use the shipped BCFKS store, set up your own first: after Phase 1, follow Option A in Default Java keystore/truststore on the FIPS page. Then run the commands below against your store to confirm neither root is in it, and delete any that are. Don't edit the shipped store; Edge updates replace it. # Path and password for the BCFKS truststore configured in /opt/apigee/customer/application/COMPONENT.properties: BCFKS_PATH="/opt/apigee/customer/application/my-cacerts.bcfks" BCFKS_PASS="YOUR_STORE_PASSWORD" # Automatically resolve the bc-fips jar version BC_FIPS_JAR=$(ls /opt/apigee/edge-gateway/lib/thirdparty/bc-fips-*.jar | head -n 1) # 1. Inspect and identify the exact alias names in the BCFKS store keytool -J-Dcom.redhat.fips=false -list \ -keystore "$BCFKS_PATH" \ -storetype BCFKS \ -storepass "$BCFKS_PASS" \ -providerclass org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider \ -providername BCFIPS \ -providerpath "$BC_FIPS_JAR" | grep -i -E "emudhra|emsign|aaa certificate|comodo" # 2. Delete the compromised aliases (replace with the exact case-sensitive alias names from step 1) sudo keytool -J-Dcom.redhat.fips=false -delete \ -alias "emsigneccrootca-g3" \ -keystore "$BCFKS_PATH" \ -storetype BCFKS \ -storepass "$BCFKS_PASS" \ -providerclass org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider \ -providername BCFIPS \ -providerpath "$BC_FIPS_JAR" sudo keytool -J-Dcom.redhat.fips=false -delete \ -alias "comodoaaaservicesroot" \ -keystore "$BCFKS_PATH" \ -storetype BCFKS \ -storepass "$BCFKS_PASS" \ -providerclass org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider \ -providername BCFIPS \ -providerpath "$BC_FIPS_JAR" # 3. Ensure file ownership remains apigee:apigee (since sudo was used) sudo chown apigee:apigee "$BCFKS_PATH" 2. Audit and Create Custom Target Server TrustStores: Review all custom TrustStores referenced by TargetEndpoint, TargetServer, or ServiceCallout TLS configurations and remove eMudhra/emSign or AAA Certificate Services certificates. If no custom TrustStore is used for outbound TLS, create and assign one to enforce explicit server certificate verification. For step-by-step guidance, see Creating keystores and truststores using the Edge UI. Phase 3: Restart Apigee Edge ServicesPerform a rolling reboot of all Apigee Edge nodes: /opt/apigee/apigee-service/bin/apigee-all stop /opt/apigee/apigee-service/bin/apigee-all start DetectionVerify OS Trust Bundle: grep -i "emSign ECC Root CA - G3" /etc/pki/tls/certs/ca-bundle.crt Step-by-Step Remediation Validation & Keystore Configuration
Apigee X/Hybrid: Review and Update Custom TrustStores (eMudhra CA Compromise)Following the compromise of intermediate Certificate Authorities associated with eMudhra (emSign) and cross-signed roots from Comodo AAA Certificate Services, Google Cloud is automatically updating Apigee X runtime and control plane platform trust bundles and releasing new versions of Apigee Hybrid. However, if your Apigee X or Apigee Hybrid API proxies use custom TrustStores in TargetEndpoint, TargetServer, or ServiceCallout configurations, you must manually inspect those TrustStores to ensure affected certificates are removed. Step 1: Identify if Custom TrustStores are in UseCustom TrustStores are configured at the environment level and referenced in your outbound TLS configurations.
Step 2: Inspect Certificates in Your TrustStoresReview the certificates contained in each custom TrustStore across your Apigee environments using either the Google Cloud console or the Apigee REST API. Option A: Using the Google Cloud console
Option B: Using the Apigee REST API
Step 3: Identify Affected CertificatesCheck if any certificate in your TrustStore matches the affected CA authorities:
Step 4: Verify Target Backend Server CertificatesBefore removing CA certificates from your TrustStore, verify that your backend servers are not actively using certificates issued by eMudhra:
Step 5: Remove Distrusted Certificates from the TrustStoreAfter verifying your target backend servers, remove any affected certificates from your Apigee TrustStore. Option A: Using the Google Cloud console
Option B: Using the Apigee REST APIDelete the certificate by alias: curl -X DELETE \ -H "Authorization: Bearer $(gcloud auth application-default print-access-token)" \ "https://apigee.googleapis.com/v1/organizations/ORGANIZATION/environments/ENVIRONMENT/keystores/KEYSTORE/aliases/CERT_ALIAS" Note: If your API proxies use a KeyStore Reference ( Vulnerability DetailsVulnerability Type: MITM / CA Compromise (CVE-2026-111943) ReferencesFor technical assistance or questions regarding custom TrustStore updates in Apigee Edge for Private Cloud, contact Cloud Customer Care or submit a ticket through the standard Apigee Support Portal. Additional Details: |
Medium |
CVE-2026-111943 CVE-2026-91403 |
GCP-2026-072
Published: 2026-10-24
Description
| Description | Severity | Notes |
|---|---|---|
|
Two vulnerabilities in PHP core, CVE-2026-109618 and CVE-2026-109619 ("PHP2Shell"), allow an unauthenticated attacker to execute code remotely on a server running a vulnerable PHP version. They are fixed in PHP 8.2.35, 8.3.36, 8.4.27, and 8.5.12. No fixed release exists for PHP 8.1 or earlier. Apigee, Apigee Hybrid, Apigee Edge for Public Cloud, API hub, and the Apigee integrated portal don't use PHP and aren't affected. Apigee Edge for Private Cloud isn't affected, apart from its optional Drupal developer portal, covered later in this bulletin. The impact is limited to Drupal-based Apigee developer portals, which customers deploy and operate. Updating the Apigee Drupal modules doesn't fix these vulnerabilities; only updating PHP does. The latest module releases ( Affected products
What should I do?Apigee Developer Portal Kickstart from Google Cloud MarketplaceNew deployments from Google Cloud Marketplace use a patched image with PHP 8.3.36. Existing deployments aren't updated automatically: patch the running VMs, then update the image. Step 1 - Patch the running VMs now. Your site, database, and files stay where they are. On each existing portal VM, run: sudo apt-get update && sudo DEBIAN_FRONTEND=noninteractive apt-get upgrade -y -o Dpkg::Options::=--force-confold sudo supervisorctl restart php-fpm sudo supervisorctl status php-fpm sudo php-fpm8.3 -v Confirm that php-fpm shows as RUNNING with a short uptime and that the last command reports PHP 8.3.36. Restart PHP-FPM with Step 2 - Move the instance group to the patched image, so VMs the group creates later are also patched. A Marketplace portal runs in a regional managed instance group with autoscaling and autohealing; a VM the group creates later boots from the instance template's image, which
Then confirm that Apigee Developer Portal Kickstart Docker imageThe If you use the prebuilt image, pull it before restarting: docker-compose pull apigee-kickstart docker-compose up -d apigee-kickstart If you build the image yourself: docker-compose build --pull apigee-kickstart docker-compose up -d apigee-kickstart Then confirm that Self-hosted Drupal 10 and Drupal 11 portalsUpdate PHP on every portal server to 8.2.35, 8.3.36, 8.4.27, 8.5.12, or a later release in the same branch. Then restart PHP-FPM or your web server.
Apigee Edge for Private Cloud Drupal 7 and Drupal 9 portalsThese portals run PHP 7.3 or 7.4 on RHEL/CentOS 7, RHEL 8, or Amazon Linux 2, where no packaged fix is available. Drupal 7 and Drupal 9 are end of life.
Apigee Edge for Public Cloud self-hosted Drupal 7 portalsAfter Apigee ended hosting of Drupal 7 developer portals on 2020-05-31, Apigee Edge for Public Cloud customers who kept their portals took over hosting them. If your portal is hosted on Pantheon or Acquia, confirm with your provider that your site runs a patched PHP version. Portals moved to a customer's own servers run whatever PHP the customer installed: on Debian or Ubuntu, PHP 7.4 can be updated in place with Sury packages, while PHP 7.3 and earlier have no fix - move to PHP 8.2 or later. Then restart PHP-FPM. Interim mitigationsThese settings reduce exposure until you can update PHP; they don't fix the vulnerabilities. Set them administratively, as
For more information, see the PHP advisories GHSA-w8hw-w9fx-j79w and GHSA-6wmf-4rv5-p3rp. For help, contact Apigee Support: for Apigee and Apigee Hybrid, see Getting started with Apigee support; for Apigee Edge and Apigee Edge for Private Cloud, see Getting started with Apigee Edge support. Check for compromiseUpdating PHP doesn't remove an attacker who exploited the portal before it was patched. Look for PHP-FPM worker processes that started shells, interpreters, |
Critical |
CVE-2026-109618 CVE-2026-109619 |
GCP-2026-041
Published: 2026-06-24
Description
| Description | Severity | Notes |
|---|---|---|
|
A recent security investigation was conducted regarding log4j vulnerabilities (CVE-2026-34480 and CVE-2026-34477) reported in Apigee Edge for Private Cloud. Google has determined that Apigee Edge for Private Cloud is not vulnerable to these CVEs. No customer action is required. CVE-2026-34480: Apache Log4j Core's CVE-2026-34477: Addressed hostname verification issues where TLS connections could be left vulnerable to interception when using SMTP, Socket, or Syslog appenders. Mitigation Note: Apigee Edge for Private Cloud only ships the log4j library in gateway components but doesn't actually use them, as logback is used instead. Furthermore, Apigee Edge for Private Cloud does not use SMTP, Socket, or Syslog appender features of log4j. As a result, neither of these vulnerabilities is applicable to Apigee Edge for Private Cloud. Affected Products
What Should I Do? Apigee Edge for Private CloudNo customer action is required. Apigee Edge for Private Cloud is not affected by these vulnerabilities. Customers running vulnerability scanners against Apigee Edge for Private Cloud deployments may see CVE-2026-34480 and CVE-2026-34477 flagged because the log4j library is present on disk. Customers can cite this security bulletin in their scanner-finding exception process to mark these CVEs as Not Applicable for their Apigee Edge for Private Cloud deployment. |
High |
CVE-2026-34480 CVE-2026-34477 |
GCP-2026-034
Published: 2026-05-20
Description
| Description | Severity | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
A vulnerability was found in Apigee where the Affected Products Impact is confined to the
What Should I Do? Take the following actions for each affected product: ApigeeNo action is required for customers using the Google Cloud version of Apigee. Vulnerability fixes have been applied to Apigee release 1-16-0-apigee-5. Apigee HybridYou must upgrade to one of the following security patch releases:
|
High | CVE-2026-2264 |
GCP-2026-010
Published: 2026-02-13
Description
| Description | Severity | Notes | ||||||
|---|---|---|---|---|---|---|---|---|
|
A vulnerability was identified in the Apigee platform that could have allowed a malicious actor with administrative or developer-level permissions in their own Apigee environment to elevate privileges and access cross-tenant data. Specifically, a vulnerability in Apigee's sandboxing technology allowed the use of a link-local endpoint to access service account tokens (P4SA) within a customer tenant project. By leveraging this identity, an attacker could theoretically read analytics metadata or tamper with internal monitoring records across other Apigee organizations (tenants). What should I do? Take the following actions for each affected product: ApigeeNo action is required for customers using the Google Cloud version of Apigee. Vulnerability fixes have been applied to Apigee release 1-16-0-apigee-3. Apigee HybridTo resolve this vulnerability, customers must enable the Pub/Sub-based analytics pipeline and upgrade to a supported hybrid version:
|
High | CVE-2025-13292 |
GCP-2025-023
Published: 2025-05-05
| Description | Severity | Notes | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
This bulletin addresses potential security gaps which could be exploited if not addressed in the JavaCallout and PythonScript policies that were discovered and addressed. These policies could lead to unauthorized remote code execution (RCE) and privilege escalation within the Apigee runtime environment. These possible exploits require internal authorized user access (users who have privilege to deploy proxies) to exploit. These potential vulnerabilities stem from insufficient sandboxing for scenarios such as access by reflection and spoofing permission objects to bypass the security manager. Affected Products Impact is confined to the JavaCallout and PythonScript policies. This includes deployments on the following Apigee platforms:
What Should I Do? Take the following actions for each affected product: ApigeeNo action is required for customers using the Google Cloud version of Apigee. Vulnerability fixes have been applied to Apigee release 1-14-0-apigee-8. If the release team is not able to make the release rollout for your orgs, either a TAM or a support representative will reach out to you to fix any affected JavaCallout proxy bundles. Apigee HybridYou must upgrade to one of the following security patch releases:
|
High |
Apigee Edge for Public Cloud
No action is required from Apigee Edge customers. Fixes have been applied to the latest Edge runtime. If you are a customer who cannot be updated to the latest Edge release due to known pending action items, a customer support representative will reach out to you.
Apigee Edge for Private Cloud
If you are an Edge for Private Cloud user, you should review your JavaCallout and PythonScript policies to ensure you are using code and libraries from trusted sources. Modifications to such policies require internal authorized access (users who have permissions to deploy proxies), so it is recommended that you audit your permissions to ensure only trusted users retain such access. Vulnerability fixes have been applied to Edge Private Cloud releases 4.52.02 and 4.53.00.
GCP-2024-040
Published: 2024-07-02
This bulletin includes details specific to each of these Apigee products:
Edge Public Cloud
| Description | Severity | Notes |
|---|---|---|
|
A remote code execution vulnerability, CVE-2024-6387, was recently discovered in OpenSSH. The vulnerability exploits a race condition that could be used to obtain access to a remote shell, enabling attackers to gain root access to GKE nodes. At the time of publication, Apigee Edge for Public Cloud is not exploitable and mitigations are in place. Even though this CVE is not exploitable, Apigee will upgrade the workloads to address the above CVE. What should I do? No action item is required from Apigee users. Patching for workloads will be done in the upcoming days and the security bulletin will be updated once the patching is completed. |
Critical |
Edge Private Cloud
| Description | Severity | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
A remote code execution vulnerability, CVE-2024-6387, was recently discovered in OpenSSH. The vulnerability exploits a race condition that could be used to obtain access to a remote shell, enabling attackers to gain root access to VM nodes. Edge Private Cloud customers own and manage the VMs/Physical hosts where Edge Private Cloud is deployed.
What should I do? Review the OpenSSH version by issuing the command |
Critical |
Edge Microgateway
| Description | Severity | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
A remote code execution vulnerability, CVE-2024-6387, was recently discovered in OpenSSH. The vulnerability exploits a race condition that could be used to obtain access to a remote shell, enabling attackers to gain root access to VM nodes. Edge Microgateway customers own and manage the VMs/Physical hosts where Edge Microgateway is deployed.
What should I do? Please review the OpenSSH version by issuing commands |
Critical |
Apigee
| Description | Severity | Notes |
|---|---|---|
|
A remote code execution vulnerability, CVE-2024-6387, was recently discovered in OpenSSH. The vulnerability exploits a race condition that could be used to obtain access to a remote shell, enabling attackers to gain root access to GKE nodes. At the time of publication, Apigee is not exploitable and mitigations are in place. Even though this CVE is not exploitable, Apigee will upgrade the workloads to address CVE-2024-6387. What should I do? No action item is required from Apigee users. Patching for workloads will be done in the upcoming days and the security bulletin will be updated once the patching is completed. Note: If Managed Instance Groups are deployed in a customer project for northbound load balancing, specifically InternalRouting (VPC) and ExternalRouting (MIG), verify the OpenSSH version installed on them. If the version is vulnerable to the CVE, then update to OpenSSH version 9.8p1 released on July 1, 2024 by yourself, as Apigee does not manage these MIGs. |
Critical |
Apigee Hybrid
| Description | Severity | Notes | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
A remote code execution vulnerability, CVE-2024-6387, was recently discovered in OpenSSH. The vulnerability exploits a race condition that could be used to obtain access to a remote shell, enabling attackers to gain root access to GKE nodes. At the time of publication, hybrid images are not vulnerable because OpenSSH is not packaged into any of the hybrid container images. However if your host/GKE-node OS is running with the below vulnerable versions of OpenSSH, your hybrid clusters will be exploitable.
What should I do? This issue has been addressed in Google Cloud Customer Care Security Bulletin GCP-2024-040. For instructions and more details, see the following bulletins:
|
Critical |
GCP-2024-006
Published: 2024-2-5
| Description | Severity | Notes |
|---|---|---|
|
When an Apigee API Management proxy connects to a target endpoint or target server, the proxy does not perform hostname validation for the certificate presented by the target endpoint or target server by default. If hostname validation is not enabled using one of the following options, Apigee proxies connecting to a target endpoint or target server may be at risk for a man-in-the-middle attack by an authorized user. For more information, see Configuring TLS from Edge to the backend (Cloud and Private Cloud). Affected Products Apigee proxy deployments on the following Apigee platforms are affected:
What Should I Do? Customers can utilize either of the following options to enable this validation: Option 1 - Add a configuration to your proxy You can enable validation of your target endpoint or target server by adding a <HTTPTargetConnection>
<SSLInfo>
<Enabled>true</Enabled>
<TrustStore>ref://mytruststoreref</TrustStore>
<CommonName>*.example.com</CommonName>
</SSLInfo>
<URL>https://my.example.com/</URL>
</HTTPTargetConnection>If this configuration is present in the Apigee recommends this approach. You can test proxies individually to confirm that validation is performing as intended, with minimal potential disruption to traffic. For more information on testing hostname validation in your proxies and viewing faults, see Using the Trace Tool. Option 2 - Set an organization-level flag You can set an Apigee organization-level flag to enable hostname validation for all deployed proxies and targets in your organization. If the Note: While this option can help you enable the feature across the organization, hostname validation failures can occur if your targets do not present the expected certificates.
Apigee recommends implementing this change in non-production environments first, to ensure that the validation works as intended and does not result in production outages. In the event that hostname validation fails for any targets, the following fault message is returned: {"fault":{"faultstring":"SSL Handshake failed java.security.cert.CertificateException: No subject alternative DNS name matching example.com found.","detail":{"errorcode":"messaging.adaptors.http.flow.SslHandshakeFailed"}}} |
High |
GCP-2023-032
Published: 2023-10-13
Updated: 2023-11-03
| Description | Severity | Notes |
|---|---|---|
|
2023-11-03 Update: Added known issue for Apigee Edge for Private Cloud. A Denial-of-Service (DoS) vulnerability was recently discovered in multiple implementations of the HTTP/2 protocol (CVE-2023-44487), including the Apigee Ingress (Cloud Service Mesh) service used by Apigee X and Apigee hybrid. The vulnerability could lead to a DoS of Apigee API management functionality. Affected Products
Unaffected products
What Should I Do?
What Vulnerabilities Are Addressed By These Patches? The vulnerability, CVE-2023-44487, could lead to a DoS of Apigee API management functionality. |
High | CVE-2023-44487 |