On October 22, 2026, we released an updated version of Apigee (1-18-0-apigee-7).
| Bug ID | Description |
|---|---|
| 573663408 | Security fix for Apigee. Upgraded the ingress gateway to patch security vulnerabilities. |
| N/A | Security fix for Apigee infrastructure. |
| Bug ID | Description |
|---|---|
| 568535165 | Skip main_task_wait_time and nio_task_wait_time metrics for the first 12 Prometheus scrapes during Message Processor startup warmup. |
| 573602919 | Fix generated OpenAPI specs' servers[] to carry the Apigee envgroup hostname instead of the backend target host. |
| 562964081 | The sgpUserIntentMatchingMode verdict-log field is now always present, including on dry-run policy records, and shows the mode used for the evaluation, including when sgpUserIntentMatching isn't set (CONSTRAINTS_AND_INTENT, or INTENT_ONLY when no policies match the tool call). |
| 524115876 | Fix an intermittent HTTP 400 error in the OASValidation policy's strict parameter validation that rejected valid requests. |
| 572025634 | Responses with a compressed text/event-stream body to a proxy with an EventFlow now skip EventFlow processing and pass through intact instead of returning a corrupted body. |
| 549078690 | If no SGP policy is attributed for a denial, a customer sees the generic fallback message. This fix short-circuits to show the rationale instead when no matched policy has a configured denial message. |
| 492041991 | VerifyAPIKey and VerifyAccessToken now set the apiproduct.operation.llmTokenQuota.* flow variables only from the LLM operation(s) that matched the request; they are no longer set from unmatched LLM operations or for requests that match no LLM operation. |
| 567244615 | Semantic Governance now evaluates LLM requests it previously skipped, such as OpenAI requests whose message content is an array of parts, which can produce new denials and judge-model usage. It considers every system message rather than only the last, and a non-streaming OpenAI or an Ollama tool call whose arguments are not valid JSON is now an evaluation error. |
| 567244615 | Semantic Governance no longer evaluates a request or response with a field it cannot read when a tool call is involved. It records verdict ERROR naming the field, with status MODEL_ERROR. The inline SemanticGovernance policy instead raises GovernedLLMResponseParseError or GovernedLLMProviderDetectionFailed (HTTP 500), in DRY_RUN too unless continueOnError is true. It also reads every text part of a Gemini system instruction and Gemini tool parameters given as parametersJsonSchema, and no longer loses the rest of a Claude or Gemini request when one field has an unexpected shape. |
| 560272924 | Added continuous-scan bidirectional gRPC streaming support for the SanitizeModelResponse policy over Server-Sent Events (SSE) streams, preserving native LLM provider SSE JSON envelopes and event framing. |
| 555332621 | Model Armor policies now honor HTTPClient.managementplane.skip.proxy: with it set, Model Armor callouts bypass the forward proxy like other googleapis traffic. Streaming (ContinuousScan) Model Armor traffic uses the forward proxy. |
| 158204922 | VerifyJWT now rejects a JWT whose header contains "b64":false, with fault steps.jwt.InvalidToken, as RFC 7797 section 7 requires. Previously, such a token could be accepted if KnownHeaders listed b64, IgnoreCriticalHeaders was true, or the header had no crit. |
| 158204922 | GenerateJWS supports RFC 7797 unencoded payloads. GenerateJWS now raises MissingPayload, InvalidPayload or FailedToResolveVariable for payload errors, where it previously raised GenerationFailed. KnownHeaders and CriticalHeaders in the JWS and JWT policies accept names separated by whitespace, such as one per line. A b64 header supplied through AdditionalHeaders is now rejected, with steps.jws.InvalidNameForAdditionalHeader for GenerateJWS and steps.jwt.InvalidNameForAdditionalHeader for GenerateJWT. A proxy that set b64 through an AdditionalHeaders variable produced an RFC 7797 JWS before this change, and must move to UnencodedPayload, with DetachContent for the detached form. |
| 158204922 | VerifyJWS verifies RFC 7797 unencoded-payload JWS (b64:false), attached or detached. b64 in crit no longer needs a KnownHeaders entry. VerifyJWS rejects b64:false unless crit lists b64, with the new fault steps.jws.UnencodedPayloadNotCritical; IgnoreCriticalHeaders does not change that. DecodeJWS reports the raw payload of such a JWS. |
| 559228730 | ext_proc: ImmediateResponse now carries any Content-Type (raw body bytes + preserved Content-Type); replies too large to buffer use StreamedImmediateResponse. |
| 544751120 | Semantic Governance Policies marked as dry run are now evaluated and logged without blocking the request. Each dry-run policy adds a second judge evaluation per tool-calling response, whose tokens are billed. Dry-run verdicts are written to the semantic-governance-policy log as separate records flagged sgpDryRunPolicyEvaluation=true; queries that count verdicts should add sgpDryRunPolicyEvaluation != true to exclude them. |
| 554114419 | Fixed: an AssignMessage/HTTPModifier/RaiseFault policy that creates a new request (createNew="true") in an HTTP/2 flow can now set the :path and :authority pseudo-headers instead of failing with an invalid-header error. |
| 567812025 | FILESYSTEM persistence mode makes the synchronizer skip Cassandra entirely (no connections, reads, writes, or datastore health probes). |
| 559009293 | Fixed elevated OAuth latency and Cassandra read load for AppGroup apps, including access token verification and token and authorization-code generation, by caching AppGroup lookups in the message processor runtime, matching Developer behavior. |
| 568860869 | Fixed RegularExpressionProtection patterns of the form "...." whose middle section contains regular expression syntax (for example, ".?Exception in thread." or "(?i).<script.>.*") being matched as literal text instead of as regular expressions. Such patterns now raise steps.regexprotection.ThreatDetected for all matching input. |
| 564945600 | Enhance VerifyAPIKey policy to better handle leading spaces. |
| 502231886 | Fixed the default source templates for SanitizeUserPrompt and SanitizeModelResponse so a policy that omits the source element extracts content correctly when IgnoreUnresolvedVariables is false. |
| 562964081 | Semantic Governance now honors the sgpUserIntentMatching AuthzExtension metadata key (ENABLED or DISABLED) to toggle user-intent matching in policy evaluation; DISABLED evaluates against constraints only. |
| 565004219 | Fixed Semantic Governance Policy skipping evaluation for Anthropic requests that send system as a content-block array (the form ADK and LiteLlm emit). Affected agents are now evaluated, which may produce new denials and new judge-model usage on the consumer project. |
| 527517087 | SGP policy logs written to your project now identify their originating region. resource.type changes from "global" to "generic_node" and the region appears in resource.labels.location. Anything selecting these entries by resource.type="global" must be updated -- including log-based metrics, sinks, exclusion filters and alerts, which stop matching silently rather than erroring. |
| 575439485 | JavaCallout policies that run remotely (per-contract offload) can now pass every value type allowed by the GCP-2025-023 setVariable restriction between policies (collections, maps, arrays, primitive wrappers including Character, Date, BigDecimal, UUID, java.time, atomics, JDK enums, Optional), with their types preserved, instead of failing with steps.remotepolicy.NonSerializableVariable. |
| 575439485 | Remotely executed (per-contract offload) JavaCallout policies with continueOnError="true" now continue the flow when the callout faults, instead of returning HTTP 500. |
| 567244901 | In enforce mode, Semantic Governance now blocks a tool call when the governance check cannot be completed, instead of letting it through. |
| 573622417 | Fixed an issue where istio-ingressgateway forwarded the x-envoy-decorator-operation header to upstream runtime and target backends. |
| 571679067 | removes old version of ApigeeTelemetry CRD. |
| 571378258 | The Apigee Redis container is now built from the Valkey engine (BSD-3-Clause, Linux Foundation) at version 8.1.10. Wire protocol is unchanged (RESP2) and the redis-server/redis-cli binary names are preserved. |
| N/A | Updates to infrastructure and libraries. |
Apigee Emulator
On October 21, 2026, we released Apigee Emulator version 2.0.2.
This release upgrades the Apigee Emulator runtime to Java 21 (Eclipse Temurin JRE 21) to align local proxy development and policy execution with the production Apigee runtime, while keeping the embedded Apache Cassandra datastore pinned to Java 8. It also addresses 46 security vulnerabilities across Netty, Jackson, Apache Log4j, BouncyCastle, Apache CXF, Eclipse Jetty, and the embedded Cassandra Go standard library health-check binary.
The emulator image is available at Artifact Registry.
To upgrade, update the emulator version in your Cloud Code for VS Code settings
to 2.0.2. See
Manage the Apigee Emulator
for details.
Apigee Emulator
21.0.12.1.0+1-0, from JRE 11 11.0.31+11), adding JVM 21 compatibility
flags (-Djava.security.manager=allow and --add-opens module flags) for
JavaCallout, JavaScript (Rhino), and Python (Jython) policies while keeping
the embedded Apache Cassandra 4.0.19 datastore pinned to Eclipse Temurin
JRE 8.4.1.137.Final (from 4.1.135.Final) and updated
netty-tcnative-boringssl-static and netty-tcnative-classes to
2.0.81.Final (from 2.0.77.Final).jackson-core, jackson-databind, and
jackson-dataformat-yaml) to 2.21.7 (from 2.18.6 and 2.19.2) and
jackson-annotations to 2.21.log4j-api and log4j-core) in
ConfigUtil.jar to 2.25.5 (from 2.17.1 and 2.25.4).bcprov-jdk18on, bcpkix-jdk18on, and
bcutil-jdk18on) to 1.85 (from 1.84).cxf-*) to 3.6.12 (from 3.5.11).1.82.3 (from 1.62.2), Protobuf (protobuf-java and
protobuf-java-util) to 4.33.6 (from 3.25.5), and Guava to 33.5.0-jre
(from 33.4.8-jre).org.eclipse.jetty:jetty-* (9.4.58.v20250814) and
commons-collections:commons-collections (3.2.2) JARs from the emulator
distribution.1.27.0
(from 1.25.11) in the embedded /opt/apigee/ready health-check binary.Apigee Emulator
This release addresses 46 security vulnerabilities across Netty, the embedded Go standard library, Jackson, Apache Log4j, Eclipse Jetty, BouncyCastle, and Apache CXF:
| CVE / Advisory | Component |
|---|---|
| CVE-2026-75595 | Netty (netty-handler) |
| CVE-2026-75596 | Netty (netty-handler) |
| CVE-2026-59901 | Netty (netty-codec) |
| CVE-2026-55831 | Netty (netty-codec-http) |
| CVE-2026-55833 | Netty (netty-codec-http) |
| CVE-2026-56745 | Netty (netty-codec-http) |
| CVE-2026-56746 | Netty (netty-codec-http) |
| CVE-2026-59898 | Netty (netty-codec-http) |
| CVE-2026-59899 | Netty (netty-codec-http) |
| CVE-2026-59903 | Netty (netty-codec-http) |
| CVE-2026-59921 | Netty (netty-codec-http) |
| CVE-2026-56819 | Netty (netty-codec-http2) |
| CVE-2026-59900 | Netty (netty-codec-http2) |
| CVE-2026-73508 | Netty (netty-codec-dns) |
| CVE-2026-39821 | Go standard library |
| CVE-2026-33818 | Go standard library |
| CVE-2026-39822 | Go standard library |
| CVE-2026-42505 | Go standard library |
| CVE-2026-56853 | Go standard library |
| CVE-2026-56858 | Go standard library |
| CVE-2026-56859 | Go standard library |
| CVE-2026-56860 | Go standard library |
| CVE-2026-56862 | Go standard library |
| CVE-2026-56864 | Go standard library |
| CVE-2026-56865 | Go standard library |
| CVE-2026-68494 | Jackson (jackson-core) |
| CVE-2026-18401 | Jackson (jackson-core) |
| CVE-2026-54512 | Jackson (jackson-databind) |
| CVE-2026-54513 | Jackson (jackson-databind) |
| CVE-2026-54514 | Jackson (jackson-databind) |
| CVE-2026-54515 | Jackson (jackson-databind) |
| CVE-2026-59888 | Jackson (jackson-databind) |
| CVE-2026-59889 | Jackson (jackson-databind) |
| CVE-2026-77310 | Jackson (jackson-databind) |
| GHSA-mhm7-754m-9p8w | Jackson (jackson-databind) |
| CVE-2025-68161 | Apache Log4j (log4j-core) |
| CVE-2026-34477 | Apache Log4j (log4j-core) |
| CVE-2026-34480 | Apache Log4j (log4j-core) |
| CVE-2026-49844 | Apache Log4j (log4j-api) |
| CVE-2026-10050 | Eclipse Jetty (jetty-security) |
| CVE-2026-2332 | Eclipse Jetty (jetty-http) |
| CVE-2024-6763 | Eclipse Jetty (jetty-http) |
| CVE-2026-6790 | Eclipse Jetty (jetty-server) |
| CVE-2026-8763 | BouncyCastle (bcprov-jdk18on) |
| CVE-2026-13506 | BouncyCastle (bcprov-jdk18on) |
| CVE-2026-50645 | Apache CXF (cxf-core) |
On October 20th, 2026, we began maintenance updates of Apigee instances configured for maintenance windows.
If you set a preferred window for maintenance for your instance, and your instance version is below 1-18-0-apigee-6, your instance will be updated to 1-18-0-apigee-6 within the next seven to 21 days. A notification containing the expected date of upgrade will be sent within the next two business days.
For more information on participating in scheduled maintenance windows, see Maintenance overview and Manage Apigee instance maintenance windows.
]]>| Bug ID | Description |
|---|---|
| 466116259 | Updated the startup script for the managed instance group (MIG) that routes external traffic to Apigee. net.ipv4.ip_forward is now written to /etc/sysctl.d/, so an instance no longer stops forwarding traffic when a reboot or an OS update resets it. The script does not change unrelated iptables NAT rules. Instances pick up the change the next time they are restarted or recreated. |
On October 2, 2026, we released an updated version of Apigee (1-18-0-apigee-6).
| Bug ID | Description |
|---|---|
| 564386425 | Security fix for Apigee. Upgraded the Apigee ingress gateway (ASM) to patch security vulnerabilities. |
| 561666530 | Security fix for Apigee. Upgraded the Prometheus library to patch the following vulnerabilities: |
| N/A | Security fix for Apigee infrastructure. |
| Bug ID | Description |
|---|---|
| 432315283 | Fixed a multi-certificate truststore so that its trust anchors take effect without a Message Processor restart when features.truststore.multi_cert_bundle.enabled is toggled at runtime; the outbound SSL context is now rebuilt automatically on any trust-anchor change. |
| 565072374 | VerifyJWT policies that use a JWKS uriRef no longer return steps.jwt.NoMatchingPublicKey on the first request after the JWKS cache TTL expires when the identity provider has rotated to a new key ID. The cache now re-fetches synchronously when its entry expires. |
| 535395491 | Extension Processor (ext_proc) denials now return the status and body that the policy or FaultRule produced, instead of always returning HTTP 500. |
| 558421499 | Apigee runtime runs on JRE 21. |
| 517953321 | The lookupcache.<n>.isEncrypted and responsecache.<n>.isEncrypted flow variables now report the per-entry on-disk encryption state of the L2 cache, rather than approximating whether the cache-encryption key is loaded. L1 cache hits report false. Review any policy conditions that rely on these flow variables. |
| 563557547 | Fixed EventFlow (Server-Sent Events) coalescing multiple events into a single policy invocation under burst load on the http-adaptor data path, which produced malformed SSE output to the client. |
| 562740573 | Apigee Analytics now populates the processing_mode dimension, distinguishing proxy traffic from extension-processor traffic. This dimension is not populated in billing-only analytics mode. |
| 357042873 | Stopped redirecting apigee-cassandra-schema-readiness init container logs to /dev/null, improving troubleshooting. Workloads undergo a rolling restart upon upgrade. |
| N/A | Updates to infrastructure and libraries. |
On September 21st, 2026, we began maintenance updates of Apigee instances configured for maintenance windows.
If you set a preferred window for maintenance for your instance, and your instance version is below 1-18-0-apigee-4, your instance will be updated to 1-18-0-apigee-4 within the next seven to 21 days. A notification containing the expected date of upgrade will be sent within the next two business days.
For more information on participating in scheduled maintenance windows, see Maintenance overview and Manage Apigee instance maintenance windows.
On September 21st, 2026, we released an updated version of Apigee (1-18-0-apigee-5).
| Bug ID | Description |
|---|---|
| 560130499 | Security fix for Apigee. Fixed a security issue in the Java Callout policy. |
| 547681234 | Security fix for Apigee. Patched CVE-2026-69247 by upgrading a third-party library used by the Apigee model-security engine. |
| 556568593 | Security fix for Apigee. Patched CVE-2026-84304 by upgrading gRPC. |
| N/A | Security fix for Apigee infrastructure. |
| Bug ID | Description |
|---|---|
| 559009293 | Fixed elevated OAuth and VerifyAPIKey latency and Cassandra read load for AppGroup apps by caching the AppGroup entity in the Message Processor runtime, matching Developer-app behavior. |
| 558888960 | Fixed distributed tracing so that the target URL is included as a span attribute in all scenarios. |
| 556750755 | Fixed EventFlow (Server-Sent Events) dropping or truncating events that follow a large (greater than 16 KB) event under load on the http-adaptor data path. |
| 553931019 | The MCP tools/list method now aggregates tools across all approved API products. |
| 531783017 | Implemented the <Enforce>true</Enforce> element of SSLInfo for a Syslog endpoint, so that the syslog target's TLS server identity is verified. |
| 554114419 | Policies can now change request pseudo-headers (for example, :path and :authority) when HTTP/2 is in use. |
| 548763108 | Blocked outbound HTTP from the Message Processor to Kubernetes-internal targets. |
| 513032450 | Restored a 15-second TCP keep-alive on the Apigee Connect control-plane connection so that a silently dropped connection recovers in seconds rather than approximately two hours. |
| N/A | Updates to infrastructure and libraries. |
Addendum to Apigee release notes dated August 27, 2026 (1-18-0-apigee-4).
| Bug ID | Description |
|---|---|
| 502540992 | Fixed an issue where the SemanticCacheLookup policy was incompatible with Vertex AI Vector Search Private Service Connect (PSC) endpoints. |
SemanticCacheLookup policy supports non-default Vector Search distance measures
Available in Apigee 1-18-0-apigee-4 and later. A new optional
<DistanceMeasureType> element accepts DOT_PRODUCT_DISTANCE (the
default, and the existing behavior), COSINE_DISTANCE,
SQUARED_L2_DISTANCE and L1_DISTANCE. The policy now compares
<Threshold> in the direction the declared measure implies, so declaring a
non-default measure requires re-tuning the threshold in the same edit. The 0-to-1 restriction on
<Threshold> is also removed.
On August 27th, 2026, we released an updated version of Apigee (1-18-0-apigee-4).
| Bug ID | Description |
|---|---|
| 507878328 | Upgraded the Apigee runtime to run on JDK 17, while maintaining backward compatibility with JDK 11. |
| 530965355 | Added an opt-in Message Processor connection-failure back-off (CWC property HTTPClient.backoff.enabled, defaults to false) that prevents the Message Processor from consuming excessive CPU when a target is completely unavailable. |
| 532793298 | Fixed an API product bug where combining a payloadOperationGroup with a REST or llmOperationGroup rejected REST/LLM traffic with a 401. |
| 534420582 | The JSONThreatProtection policy adds a new optional child element <RejectDuplicateKeys> that rejects request bodies containing duplicate JSON keys within the same object. Defaults to false to preserve existing behavior. |
| N/A | Updates to infrastructure and libraries. |
This list is incomplete; see entries for September 9, 2026 and September 10, 2026.
| Bug ID | Description |
|---|---|
| 544570126 | Security fix for Apigee. Fixed a security issue in the PythonScript policy. |
| N/A | Security fix for Apigee infrastructure. |
On August 13th, 2026, we began maintenance updates of Apigee instances configured for maintenance windows.
If you set a preferred window for maintenance for your instance, and your instance version is below 1-18-0-apigee-2, your instance will be updated to 1-18-0-apigee-2 within the next seven to 21 days. A notification containing the expected date of upgrade will be sent within the next two business days.
For more information on participating in scheduled maintenance windows, see Maintenance overview and Manage Apigee instance maintenance windows.
On August 13th, 2026, we released an updated version of Apigee (1-18-0-apigee-3).
| Bug ID | Description |
|---|---|
| 532147587 | To fix forward proxy support. |
| 537657987 | Fixed a bug where watcher failed to reconcile all routes if an environment was not found in the control plane. |
| 543022076 | Google Cloud BOM upgrade (protobuf 4.x, gRPC 1.81, Guava 33.5). One user-visible change: a malformed inbound gRPC request frame is now reported to the client as grpc-status INTERNAL(13) and recorded in analytics as x-apigee.grpc.status=13, where it was previously an Apigee ServiceUnavailable fault seen as UNAVAILABLE(14) with no x-apigee.grpc.status recorded. Otherwise no user facing impact, but any prod issue related to gcp, protobuf or gRPC may relate to this. |
| 542242046 | Fixed LLMTokenQuota metering the request against an arbitrary quota bucket when the API Product declared multiple models and the request carried no model. |
| 531731614 | Apigee analytics fields ai_llm_response_token_count, ai_llm_prompt_token_count, ai_llm_model_name, and ai_llm_model_provider are available in the Custom Report when LLMTokenQuota and PromptTokenLimit policies are used in Apigee proxies. |
| 492044413 | LLMTokenQuota resolves the model from the API Product LLM Operation when LLMModelSource is omitted and the request body has no model field. |
| 67169710 | Adds an opt-in <DynamicClientIdSupported> boolean XML element to the OAuthV2 policy. When true, AbstractOAuthStepExecution.extractClientDetails() preserves any non-empty ClientID/ClientSecret already present on the OAuthClientContext. |
| 531731614 | Apigee auto identifies the providers and publishes them to analytics. |
| 537396574 | Added feature to rotate the apigee-ca certificate. |
| 540861752 | Aligned the ApigeeDeployment conversion hub with its v1alpha3 storage version. Internal change; no effect on existing ApigeeDeployment resources. |
| 540861752 | Aligned the ApigeeDeployment custom resource's conversion hub with its v1alpha3 storage version. This internal change does not affect existing ApigeeDeployment resources. |
| N/A | Updates to infrastructure and libraries. |
| Bug ID | Description |
|---|---|
| 535928300 | Security fix for Apigee. Fixed a security issue in JWT refresh token revocation handling. |
| 539515020 | Security fix for Apigee. Fixed a security issue in the MessageValidation policy. |
| 535928530 | Security fix for Apigee. Fixed a security issue in the OAuthV2 policy. |
| 535683286 | Security fix for Apigee. Fixed a security issue in HTTP target interim-response handling. |
| N/A | Security fix for Apigee infrastructure. |
On July 27th, 2026, we released an updated version of Apigee (1-18-0-apigee-2).
SanitizeUserPrompt and SanitizeModelResponse policies now support function calling
The SanitizeUserPrompt and SanitizeModelResponse policies now handle LLM function calling (tool use) flows. Two new optional XML elements extract function calling content for Model Armor sanitization:
<FunctionResponseSource> in SanitizeUserPrompt: extracts function/tool
response data from user turns. Used as a fallback when <UserPromptSource>
returns empty on function calling turns.<FunctionCallSource> in SanitizeModelResponse: extracts function call
arguments from model responses. Used as a fallback when <LLMResponseSource>
returns empty.Default templates target the Gemini format and require no additional configuration. For OpenAI and Anthropic formats, configure custom JSONPath templates. For more information, see FunctionResponseSource and FunctionCallSource.
| Bug ID | Description |
|---|---|
| 534852923 | Security fix for Apigee. Fixed a security issue in the Java Callout policy. |
| N/A | Security fix for Apigee infrastructure. |
| Bug ID | Description |
|---|---|
| N/A | Updates to infrastructure and libraries. |
On July 16th, 2026, we began maintenance updates of Apigee instances configured for maintenance windows.
If you set a preferred window for maintenance for your instance, and your instance version is below 1-17-0-apigee-10, your instance will be updated to 1-17-0-apigee-10 within the next seven to 21 days. A notification containing the expected date of upgrade will be sent within the next two business days.
For more information on participating in scheduled maintenance windows, see Maintenance overview and Manage Apigee instance maintenance windows.
]]>On July 15th, 2026, we released an updated version of Apigee (1-18-0-apigee-1).
| Bug ID | Description |
|---|---|
| 527586459 | Fixed a cache policy throttling bug (CacheThrottlerV2 key poisoning) to enhance reliability. |
| 525697701 | Fixed an issue where API proxy deployments could get stuck during basepath migrations in Apigee X. |
| N/A | Updates to infrastructure and libraries. |
| Bug ID | Description |
|---|---|
| 527415966, 524656652 | Security fix for Apigee. Upgraded the Apigee ingress gateway (ASM) to patch security vulnerabilities. |
| 527956223 | Security fix for Apigee. Enhanced security in the Java Callout policy to prevent sandbox escape. |
| 519729209 | Security fix for Apigee. Fixed a SAML XML Signature Wrapping (XSW) vulnerability in the ValidateSAMLAssertion policy. |
| 530886487 | Security fix for Apigee. Upgraded the apigee-connect-agent to patch CVE-2026-25680. |
| N/A | Security fix for Apigee infrastructure. |
An Improper Input Validation vulnerability in BigQuery DAO in Google Cloud Apigee versions prior to 2026-06-12 on Google Cloud Platform allowed an authenticated attacker to exfiltrate cross-tenant data.
This vulnerability was patched on 12 June 2026 on the Apigee Servers, and no customer action is needed. Apigee hybrid was not affected.
For more information, see CVE-2026-12879.
]]>Support for payload operations matching in API Products
Apigee now supports payload operations matching (payloadOperationGroup) in API
Products, powered by the new ParsePayload policy.
Payload operations matching allows you to define API Product operations that match fields within request payloads, such as JSON-RPC requests used by the Model Context Protocol (MCP). Apigee can then route, monetize, authorize, and apply distinct quota limits to traffic based on the derived payload operation.
This feature is available to all Apigee X customers in all supported regions with no additional charge. For more information, see Manage MCP tool access with API products and the ParsePayload policy reference.
]]>Apigee Emulator
On June 24, 2026, we released Apigee Emulator version 2.0.1.
This is a security-only hotfix release on top of v2.0.0 that addresses 10 security vulnerabilities in the Netty networking library and the embedded Cassandra Go standard library health-check binary. There are no functional, API, or configuration changes -- v2.0.1 is a drop-in replacement for v2.0.0.
The emulator image is available at Google Artifact Registry.
To upgrade, update the emulator version in your VS Code Cloud Code settings
to 2.0.1. See
Manage the Apigee Emulator
for details.
Apigee Emulator
4.1.135.Final (from 4.1.133.Final) and pinned all
transitive netty-* artifacts via netty-bom.1.25.11
(from 1.25.10) in the embedded health-check binary.netty-tcnative-boringssl-static classifier variants from
2.0.53.Final to 2.0.77.Final.Apigee Emulator
This release addresses 10 security vulnerabilities in the Netty networking
library and the embedded Go standard library. All Netty fixes come from
upgrading to 4.1.135.Final; all Go standard library fixes come from a
Cassandra base image rebuild against Go 1.25.11.
| CVE | Component |
|---|---|
| CVE-2026-50010 | Netty (netty-handler) |
| CVE-2026-50020 | Netty (netty-codec-http) |
| CVE-2026-50560 | Netty (netty-codec-http2) |
| CVE-2026-48043 | Netty (netty-codec-http2) |
| CVE-2026-44249 | Netty (netty-handler) |
| CVE-2026-45416 | Netty (netty-handler) |
| CVE-2026-47244 | Netty (netty-codec-http2) |
| CVE-2026-27145 | Go standard library |
| CVE-2026-42504 | Go standard library |
| CVE-2026-42507 | Go standard library |
On June 22nd, 2026, we released an updated version of Apigee (1-17-0-apigee-10).
| Bug ID | Description |
|---|---|
| 519996459 | Security fix for Apigee. Upgraded the Apigee ingress gateway to patch the following vulnerabilities:
|
| N/A | Security fix for Apigee infrastructure. |
| Bug ID | Description |
|---|---|
| 515788622 | Upgraded the default outbound TLS protocol from TLSv1.2 to TLSv1.3 on JVMs that support it. Per-proxy <SSLInfo><Protocols> settings continue to take precedence, and the new HTTPClient.outbound.tls.protocol override lets operators force a specific protocol. |
| 184266748 | Fixed an issue where ApigeeDatastore TLS certificate creation could fail in namespaces with longer names when the certificate common name exceeded the 64-byte limit. |
| 286069772 | Added a per-gateway proxyProtocol.mode property (strict, permissive, disable) on Apigee ingress gateway components to opt in to HAProxy PROXY-protocol parsing. The property defaults to disable. |
| N/A | Updates to infrastructure and libraries. |
On June 18th, 2026, we began maintenance updates of Apigee instances configured for maintenance windows.
If you set a preferred window for maintenance for your instance, and your instance version is below 1-17-0-apigee-9, your instance will be updated to 1-17-0-apigee-9 within the next seven to 21 days. A notification containing the expected date of upgrade will be sent within the next two business days.
For more information on participating in scheduled maintenance windows, see Maintenance overview and Manage Apigee instance maintenance windows.
]]>On June 8th, 2026, we released an updated version of Apigee (1-17-0-apigee-9).
| Bug ID | Description |
|---|---|
| 514384893 | Security fix for Apigee. Hardened the Script policy to block server-side request forgery (SSRF) to link-local addresses. |
| N/A | Security fix for Apigee infrastructure. |
| Bug ID | Description |
|---|---|
| 512850756 | Added observability metrics for the OpenTelemetry trace export pipeline, reporting spans exported, export latency, batch size, and dropped spans. |
| 515039499 | Fixed an issue where OpenTelemetry trace export over HTTP could fail to authenticate when sent through a forward proxy that requires basic authentication. |
On June 2nd, 2026, we released an updated version of Apigee Cassandra.
| Bug ID | Description |
|---|---|
| Apigee Cassandra security update | Security fix for Apigee Cassandra infrastructure. This addresses the following vulnerabilities: |
On May 29, 2026, we released an updated version of the Apigee UI.
Apigee EventFlow now supports the DataCapture policy
You can now use the DataCapture policy within an EventFlow to extract and persist data from server-sent events (SSE) streams, such as token counts and other fields from streaming LLM responses. For more information, see Use the DataCapture policy to capture token counts.
Manage Spaces in the Apigee UI
You can now create, view, update, and delete spaces, and manage their Identity and Access Management (IAM) policies directly in the Apigee UI. Previously, these actions could only be performed using the Apigee API. For more information, see Apigee Spaces overview.
]]>Apigee Emulator
On May 22, 2026, we released Apigee Emulator version 2.0.0.
Starting with this release, the Apigee Emulator is versioned and released independently from Apigee hybrid. This enables faster delivery of security patches and updates without waiting for hybrid release cycles. The emulator image continues to be available at Google Artifact Registry.
To use the new version, update the emulator version in your VS Code Cloud Code
settings to 2.0.0. See
Manage the Apigee Emulator
for details.
Apigee Emulator
Apigee Emulator
This release addresses 78 security vulnerabilities across Cassandra base image, Go standard library, Java dependencies, and Python packages. Key fixes include:
| CVE | Component |
|---|---|
| CVE-2022-42003 | Jackson Databind |
| CVE-2022-42004 | Jackson Databind |
| CVE-2022-38749 | SnakeYAML |
| CVE-2022-38750 | SnakeYAML |
| CVE-2023-2976 | Google Guava |
| CVE-2020-8908 | Google Guava |
| CVE-2024-12798 | Logback |
| CVE-2025-22866 | Go stdlib |
| CVE-2025-22870 | Go stdlib |
| CVE-2022-40897 | Python setuptools |
And 68 additional CVEs fixed through updated upstream dependencies.
]]>On May 21st, 2026, we released an updated version of Apigee (1-17-0-apigee-8).
| Bug ID | Description |
|---|---|
| 514973778 | Fixed Model Armor response parsing to gracefully handle unknown fields, so future Model Armor field additions no longer cause policy failures. |
On May 20, 2026, we published a security bulletin for Apigee.
A vulnerability was found in Apigee
(CVE-2026-2264)
where the IntegrationRegion
parameter in the SetIntegrationRequest policy lacks validation,
allowing for Server-Side Request Forgery (SSRF) and service account token
exfiltration. The issue arises when an attacker can control a flow variable used
for IntegrationRegion, leading to requests being sent to an
attacker-controlled host with the service account token.
Security bulletin published: GCP-2026-034
]]>On May 12th, 2026, we released an updated version of Apigee (1-17-0-apigee-7).
| Bug ID | Description |
|---|---|
| 511325186, 505460952, 502250074, 491231600, 497357701, 509560467, 496969438, 495897297, 495033618, 511332617, 505183435, 500735547, 500890221 | Security fix for Apigee infrastructure. This addresses the following vulnerabilities: |
| Bug ID | Description |
|---|---|
| 480260846 | Improved XML processing security to prevent external entity injection. |
| 510061670, 505723451, 503723862, 503817773 | Improved security in OAuthV2 policy. |
| 505645076 | Fixed a security issue in OAuthV2 policy to prevent unauthorized token injection. |
| 503047744, 410026138, 496021751 | Improved security isolation for PythonScript policy execution. |
| 469694040 | Fixed an issue where custom security policies could intermittently fail to apply, and improved security policy resolution to ensure correct policy selection. |
| 502971220 | Fixed a concurrency issue to improve stability under high load. |
| 509692565 | Fixed content-length header handling in external processing to prevent incorrect values. |
| 282207038 | Improved performance while listing apps on scale. |
| 501102321 | Fixed recurring fee calculation in monetization to correctly apply rate plan overrides. |
| 449729840, 502604752 | Fixed streaming response handling to prevent race conditions in bidirectional flows. |
| 507167063 | Fixed preservation of client request IDs during proxy chaining. |
| 507580304 | Improved IPv4 address normalization for consistent access control evaluation. |
| 502692267 | MCP to handle /.well-known/oauth-protected-resource/mcp resource paths. |
| 430170696 | Changed the error response from 500 to 401 for expired consumer keys. |
| 480770263 | Fixed SpikeArrest policy to handle edge cases that previously caused 500 errors. |
| 500861814 | Gracefully handle connection failures involving the forward proxy, resolving an issue where port exhaustion could trigger aggressive retry storms, excessive CPU usage, and unnecessary scaling. |
| 500313309 | Fixed SSE streaming detection logic. |
| 494304819 | Hardened message processor management ports by blocking external access to internal management endpoints. |
| 469642464 | Improved input validation in AI protection policies to prevent Server-Side Request Forgery. |
| 472526232 | Improved SAML assertion validation. |
| 494590020 | Added enforcement for product association in OAuthV2 flow. Apps without valid products are now denied. |
| 479288727 | Improved performance and reduced redundant work in ingress status watcher. |
| N/A | Updates to infrastructure and libraries. |
On April 29th, 2026, we began maintenance updates of Apigee instances configured for maintenance windows.
If you set a preferred window for maintenance for your instance, and your instance version is below 1-17-0-apigee-4, your instance will be updated to 1-17-0-apigee-4 within the next seven to 21 days. A notification containing the expected date of upgrade will be sent within the next two business days.
For more information on participating in scheduled maintenance windows, see Maintenance overview and Manage Apigee instance maintenance windows.
]]>Relaxed limitation on header name for Client IP resolution
The client IP can now be resolved from any header, not just the X-Forwarded-For header. The most common headers are X-Forwarded-For or True-Client-Ip.
For more information, see Client IP resolution.
]]>Correction to April 2, 2026 release note: Deployment disruption for Apigee Drupal Portal via Google Cloud Marketplace
For the deployment disruption announced on April 2, the announcement noted that deployment and management functionality using Google Cloud Deployment Manager would definitely be unavailable during the transition. This statement is incorrect. The functionality might be unavailable.
See the Known issue for more information.
On April 6th, 2026, we released an updated version of Apigee.
This change introduces the new apigee.coreServiceAgent IAM role for
Apigee. Effective immediately, use apigee.coreServiceAgent instead of the
apigee.serviceAgent role.
For information on the new role, see
apigee.coreServiceAgent.
Deployment disruption for Apigee Drupal Portal via Google Cloud Marketplace
Google Cloud Deployment Manager was deprecated as of March 31, 2026. We are currently transitioning the Apigee Drupal Portal Marketplace solution to use Infrastructure Manager. During this transition period, some deployment and management functionalities are unavailable.
Impact:
gcloud deployment-manager tool.Workaround & Resolution: Any configuration changes or management tasks must be performed directly on the individual Google Cloud resources (Compute Engine, Cloud SQL, etc.) rather than through the Marketplace UI.
We are actively working to release the updated Infrastructure Manager-based solution.
]]>On March 31st, 2026, we released an updated version of Apigee.
General Availability (GA) launch of Model Context Protocol (MCP) in Apigee
With this release, Model Context Protocol (MCP) in Apigee is generally available, enabling you to expose your Apigee APIs as MCP tools to agentic applications.
Any MCP client that supports remote MCP endpoints over HTTP/S can access these tools. Because the endpoints are managed, you don't need to install or manage local MCP servers, remote MCP servers, or additional infrastructure to enable agentic applications to access your services.
MCP in Apigee is available for Subscription, Pay-as-you-go, and Evaluation organizations, including organizations with Data Residency and VPC Service Controls enabled.
For more information on using MCP in Apigee, see MCP in Apigee overview.
Enhanced OAS server URL path handling for MCP in Apigee
With this feature enhancement, your OpenAPI specification (OAS) configurations behave exactly
as defined in the OAS standard, automatically combining the server.url base path value with individual operation paths.
For example, a server URL ofhttps://example.com/api/v1 paired with a path of /users will now correctly route to https://example.com/api/v1/users without additional manual intervention.
If you previously prepended base paths to your OAS paths entries, remove the path segment from your servers.url field to prevent
duplication. For example, change https://example.com/api/v1 to https://example.com.
For more information, see Create an OpenAPI 3.0 specification.
Updated MCP server target endpoint for MCP Discovery Proxies
With the GA launch of Model Context Protocol (MCP) in Apigee, the structure of the MCP server target endpoint for MCP Discover Proxies has changed to ORG_NAME.mcp.apigee.internal.
Private preview customers using the previous format (mcp.apigee.internal) are encouraged to update their proxies to reflect the new structure. Existing endpoints using the old format will continue to work, but new endpoints will use the new structure.
Known Issue 496552286: Deployment fails for MCP Discovery Proxies in regions with capacity limitations.
For more information, see Apigee known issues.
]]>