Getting started Community Training Tutorials Documentation APIs, AI & Tools
Omni Gateway no longer sends runtime log records that have no message.
These release notes reflect enhancements, changes, and bug fixes for Omni Gateway.
In addition to these release notes, see:
November 19, 2026
MuleSoft announces the release of Omni Gateway 1.15.0.
Envoy is now upgraded to version 1.40.0.
Fluent Bit is now upgraded to version 5.1.3.
Omni Gateway and the Schema Validation policy now support OpenAPI Specification (OAS) 3.1 and 3.2 for REST API instances.
Omni Gateway now supports Red Hat Enterprise Linux (RHEL) 10.
You can now configure default inbound and outbound TLS context that apply to all API instances and upstream services that use https:// paths. Applying a TLS policy or a TLS context in the UI overrides the default TLS context. The outbound default also applies to outbound calls made by policies.
For Local Mode gateways, configure default TLS contexts by using the defaultTLS.inbound and defaultTLS.outbound fields of the Configuration resource. The defaultTLS.outboundPolicyCalls field is deprecated. Use defaultTLS.outbound instead. If both fields are set, Omni Gateway ignores defaultTLS.outboundPolicyCalls.
In Connected Mode and managed gateways, configure the default inbound and outbound TLS contexts configured in Runtime Manager.
For managed gateways on Runtime Fabric with last-mile security enabled, a default inbound TLS context that includes a keystore replaces the generated self-signed certificate.
Managed Omni Gateway on Runtime Fabric now uses the forward proxy settings of Runtime Fabric. You no longer need to apply a Configuration resource to each gateway to configure the proxy.
You can now configure a correlation ID for all API instances.
The Correlation ID Override policy is added to override the global correlation ID header and generation expression for a single API instance.
The External Authorization policy now supports caching authorization decisions per client identity. Matching requests skip the call to the authorization service. Authorization service errors and timeouts are never cached.
The DataWeave Body Transformation Outbound and DataWeave Headers Transformation Outbound policies are added to transform, with a DataWeave script, the body or headers of requests sent to a specific upstream service and of its responses.
The Credential Injection OAuth 2.1 Token Broker (Authorization Code) policy is added to inject each user’s own upstream access token into outbound requests. When no token is available, the policy returns a link that the user follows to connect their account.
The OAuth 2.1 Token Broker Connect (Authorization Code) policy is added to host the browser login and consent flow for connecting upstream accounts. The policy also presents authorization-required responses in a format that MCP clients understand.
In Connected Mode, Runtime Manager runtime configurations now take precedence over Configuration resources. To adjust precedence the edit the flex.mulesoft.com/resource-priority label in the Configuration resource.
For an example of how to set the priority value, see Runtime Manager Runtime Configuration and Configuration Resource Priority.
Base-path canonicalization is now enabled by default in all Self-Managed Omni Gateway deployments. To restore the previous behavior, set FLEX_BASE_PATH_CANONICALIZER_ENABLED to false.
Configuration caching (control node) now encrypts cached data from Anypoint Platform, such as private keys and client secrets, in shared storage. By default, the encryption key is derived from the registration private key. To use a different key, set FLEX_STORAGE_ENCRYPTION_KEY. To disable encryption, set FLEX_CONTROL_NODE_STORAGE_ENCRYPTION_ENABLED to false. Existing data isn’t migrated. To encrypt it, run flexctl reset and restart all replicas. Replicas running earlier versions and 1.15.0 replicas can’t share the same Redis storage.
Omni Gateway now uses the X-Forwarded-Host header for host-based routing and policy rule matching. If a request doesn’t include it, Omni Gateway sets it from the Host header, so upstream services also receive it.
You can now set how long Omni Gateway in Connected Mode waits for the initial configuration to settle at startup with the FLEX_STARTUP_DEBOUNCE_TIME environment variable or the gateway.startupDebounceTime Helm value.
The Omni Gateway Helm chart can now create a PodDisruptionBudget (podDisruptionBudget.enabled, default maxUnavailable: 1) and a VerticalPodAutoscaler (verticalPodAutoscaler.enabled, default updateMode: Off) for the gateway Deployment. The VerticalPodAutoscaler requires the Kubernetes Vertical Pod Autoscaler in the cluster.
Omni Gateway deployments managed by Runtime Fabric now support custom labels set through kubernetes.deployment.metadata.labels in a KubernetesTemplate custom resource. These labels apply to the Deployment, its pods, and related resources. The reserved app and version labels can’t be overridden.
Omni Gateway no longer sets the CAP_NET_BIND_SERVICE file capability on the Envoy binary. The flex-gateway systemd service now grants it instead. For container deployments outside the Helm chart that listen on ports below 1024, allow unprivileged port binding (net.ipv4.ip_unprivileged_port_start) or grant the NET_BIND_SERVICE capability.
| Issue Resolution | ID |
|---|---|
Omni Gateway no longer sends runtime log records that have no message. |
W-24430178 |
The DataWeave and SOAP Schema Validation policies no longer omit their logs from the Omni Gateway logs. These logs now include the policy, API instance, and request ID, and respect the configured log level. |
W-24078475 |
Omni Gateway no longer leaves empty or incomplete |
W-12717907 |
The |
W-23969867 |
The Schema Validation policy no longer fails to apply when an OAS 3.0 specification includes |
W-24409155 |
These vulnerabilities detected by scanners are now fixed: |
W-23425257, W-24470081 |
November 18, 2026
MuleSoft announces the release of Omni Gateway 1.14.5.
You can now configure the Redis shared storage timeout and number of retries with the new optional timeoutMilliseconds and maxRetries fields in the sharedStorage.redis configuration resource. If you don’t set these fields, Omni Gateway uses a two-second timeout and one retry, instead of the previous five-second connect timeout, three-second read and write timeout, and three retries. To keep behavior similar to previous versions, set timeoutMilliseconds: 3000 and maxRetries: 3.
The Credential Injection API Key policy now supports removing specified headers, such as an existing Authorization header, from the request before injecting the credential.
The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies now receive the consumer URL for protected resource metadata from the API instance’s configuration, so they no longer need to retrieve it from Anypoint API Manager.
Envoy is now upgraded to version 1.37.11.
| Issue Resolution | ID | ||
|---|---|---|---|
Omni Gateway no longer drops non-standard ports from the |
W-22512224 |
||
Omni Gateway no longer returns |
W-24767532 |
||
When tracing is enabled, Omni Gateway no longer adds the |
W-24472278 |
||
The Health Check policy now reports violations as blocked requests, so they’re counted as policy violations and trigger the configured alerts. |
W-24513215 |
||
The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies no longer return a |
W-24279775 |
||
Disk and distributed shared storage no longer remove entries from stores configured without expiration (TTL |
W-24887572 |
||
The JWT Validation policy no longer fails to apply when custom claim validation is enabled and only mandatory custom claims are configured. |
W-24532054 |
||
Omni Gateway no longer wraps error responses of SOAP API instances in another SOAP fault when the response is already a SOAP 1.1, SOAP 1.2, or multipart (MTOM/SwA) message. SOAP faults generated by Omni Gateway now use the SOAP version of the request envelope. |
W-24945734 |
||
The SOAP Schema Validation policy no longer chooses the SOAP version of its fault responses based on the |
W-24945734 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-24764986, W-24765178 |
October 23, 2026
MuleSoft announces the release of Omni Gateway 1.14.4.
Custom PDK policies can now access an API instance’s configured consumer URL through api.consumerUri in API Context.
| Issue Resolution | ID | ||
|---|---|---|---|
Omni Gateway now rejects certificates chaining through known compromised eMudhra intermediate certificates. |
W-24628768 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-24624014 |
October 20, 2026
MuleSoft announces the release of Omni Gateway 1.14.3.
Envoy is now upgraded to version 1.37.8.
Tracing custom labels now support integer, floating-point, and boolean OpenTelemetry attributes, and values resolved through Envoy substitution expressions.
The Credential Injection API Key policy now supports DataWeave expressions to resolve the API key from request attributes or payloads at runtime.
| Issue Resolution | ID | ||
|---|---|---|---|
Path normalization is now disabled by default. To enable it, set |
W-24443266 |
||
Helm deployments now preserve a configured API address trailing slash and enable base-path canonicalization by default. APIs configured with a slashless base path can accept requests to that exact base path. |
W-24541915 |
||
Omni Gateway now uses |
W-24279051 |
||
Runtime Fabric Helm deployments now normalize wildcard-prefixed forward-proxy exclusions and omit unsupported CIDR entries. |
W-24460337 |
||
Helm-generated inbound TLS bindings now apply the correct TLS-context precedence when APIs share a listener. |
W-24511699 |
||
Gateway-agent configuration generation now uses less memory when multiple distinct WebAssembly policies are applied. |
W-24390601 |
||
The Injection Protection policy no longer incorrectly rejects legitimate multipart SOAP requests with binary attachments when body scanning is enabled. |
W-24361237 |
||
The JWT Validation policy now accepts RSA keys with padded base64url parameters in JWKS responses. |
W-24309516 |
||
Control-node replicas now retry concurrent revision updates with backoff instead of failing deployments with a precondition error. |
W-24580345 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-24456219, W-24578725 |
October 1, 2026
MuleSoft announces the release of Omni Gateway 1.14.2.
| Issue Resolution | ID |
|---|---|
The JWT Validation, OpenID Connect OAuth 2.0 Token Enforcement, and OAuth 2.0 Token Introspection policies now preserve path segments and trailing slashes from consumer URLs when generating protected resource metadata URLs. |
W-24119444 |
Omni Gateway now preserves percent-encoded reserved characters, such as |
W-24135806 |
Per-API message logs in API Manager now populate correctly for Omni Gateway registrations that use v1 URLs. |
W-24332213 |
September 25, 2026
MuleSoft announces the release of Omni Gateway 1.14.1.
Managed Omni Gateway deployments on Runtime Fabric now support forward proxy configuration.
Configuration resources now support environment variable expansion in string and scalar values.
Self-Managed Omni Gateway can now internally rewrite requests that exactly match a configured slashless API base path, such as /api, to its slash-terminated form (/api/). Set FLEX_BASE_PATH_CANONICALIZER_ENABLED to true to enable this behavior.
The Message Logging policy now supports masking regex capture groups while preserving the rest of the matched value.
| Issue Resolution | ID | ||
|---|---|---|---|
Configuration caching (control node) reliability is improved, including Redis recovery, deployment status, and configuration synchronization. |
W-22456427 |
||
Log records larger than 32 KB no longer split into separate lines that lose their logging metadata. Oversized records are truncated instead. |
W-24055090 |
||
Omni Gateway running in Connected Mode no longer sends duplicate runtime logs to Anypoint Platform after logging configuration changes. |
W-24037601 |
||
Managed Omni Gateway deployments on Runtime Fabric no longer fail when the same image pull secret is supplied twice. |
W-24195540 |
||
The Basic Authentication: LDAP policy no longer includes sensitive authentication data in logs. |
W-24118398 |
||
The OpenID Connect OAuth 2.0 Token Enforcement policy now correctly applies |
W-24268807 |
||
Tracing now preserves custom server span names without forwarding the |
W-23923463 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-24126253 |
September 2, 2026
MuleSoft announces the release of Omni Gateway 1.14.0.
The JavaScript Scripting policy is added to run a user-supplied JavaScript module that can inspect and modify requests and responses directly from the gateway.
The GraphQL Access Control policy is added to authorize incoming GraphQL requests by evaluating Cedar-based access-control rules.
Local storage is now file-based instead of in-memory. State used by policies such as Rate Limiting and HTTP Caching are now retained when Omni Gateway is stopped or restarted.
Configuration caching (control node) is now enabled by default. The FLEX_DATASOURCE_CONTROL_NODE_ENABLED environment variable now defaults to true. To disable it, set the variable to false.
The OpenID Connect OAuth 2.0 Token Enforcement policy now exposes the Validated Token TTL (maxFederationExpirationTime) and Maximum Cache Entries (maxCacheSize) settings in Connected Mode to control how long validated tokens are cached and how many entries are stored.
The JWT Validation policy now supports OAuth 2.0 Protected Resource Metadata (RFC 9728). When enabled, the policy serves a discovery document at the .well-known/oauth-protected-resource endpoint and adds a resource_metadata hint to the WWW-Authenticate header of 401 responses, so clients can locate the authorization server that protects the API.
The Credential Injection OAuth 2.0 policy now supports adding custom parameters, such as audience, to the OAuth 2.0 token request body.
The Message Logging policy now supports data masking to detect and mask personally identifiable information (PII), such as email addresses, in log messages before they are written. You can select built-in PII types (Email, US SSN, Credit Card, and Phone Number) or add custom regex patterns. Data masking is available for both inbound and outbound message logging, and request and response bodies are forwarded to the upstream service unchanged.
The Schema Validation policy now validates multipart/form-data requests against their OAS schema definitions, in addition to application/json request bodies.
You can now configure the DNS refresh rate for upstream service clusters by setting the FLEX_DNS_REFRESH_RATE environment variable. The value is clamped between 5s and 60s, and defaults to 5s.
The flexctl dump CLI command now collects a full snapshot of the gateway’s runtime state into a single ZIP file, including resources, logs, and Envoy statistics. You can write the snapshot to a specific path or stream it to standard output.
The implementation of the DataWeave and SOAP policies is updated to improve policy performance, delivering higher throughput and lower latency.
The flexctl check http command now produces curl-style verbose output, logging request and response headers with > and < prefixes and writing the response body to standard output for easier scripting and inspection.
Flex Gateway deployments managed by Runtime Fabric for Kubernetes now support pod scheduling customizations (node selectors, tolerations, and affinity rules) defined through a KubernetesTemplate custom resource. Customizations take precedence over the corresponding chart-level settings when both are present.
Omni Gateway Docker images are now based on Debian 13 Distroless.
| Issue Resolution | ID | |||
|---|---|---|---|---|
The SOAP Validation policy no longer leaks temporary directories during configuration delivery. It now loads schema files whose paths contain spaces. |
W-23442789 |
|||
The WebSocket Connection Limit policy no longer omits rejected connections from the policy violations reported to Anypoint Monitoring. |
W-23173354 |
|||
Flex Gateway no longer rejects valid requests when an API specification (OAS) uses a decimal |
W-23192298 |
|||
Omni Gateway no longer reports as ready when a deployment has failed (for example, when assets could not be downloaded), even when |
W-23543048 |
|||
Flex Gateway no longer hangs when its shared storage configuration changes while the gateway is running. |
W-23573044 |
|||
Flex Gateway no longer fails to generate a valid FluentBit log configuration when a label used for log metadata (on the gateway, an API instance, or a service) has an empty value or contains spaces. |
W-23147140 |
|||
Flex Gateway no longer panics when the |
W-23950422 |
|||
These vulnerabilities detected by scanners are now fixed:
|
W-22733262 |
November 17, 2026
MuleSoft announces the release of Omni Gateway 1.13.9.
You can now configure the Redis shared storage timeout and number of retries with the new optional timeoutMilliseconds and maxRetries fields in the sharedStorage.redis configuration resource. If you don’t set these fields, Omni Gateway uses a two-second timeout and one retry, instead of the previous five-second connect timeout, three-second read and write timeout, and three retries. To keep behavior similar to previous versions, set timeoutMilliseconds: 3000 and maxRetries: 3.
The Credential Injection API Key policy now supports removing specified headers, such as an existing Authorization header, from the request before injecting the credential.
The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies now receive the consumer URL for protected resource metadata from the API instance’s configuration, so they no longer need to retrieve it from Anypoint API Manager.
Envoy is now upgraded to version 1.37.11.
The OpenTelemetry Collector is now upgraded to version 0.164.0.
| Issue Resolution | ID | ||
|---|---|---|---|
Omni Gateway no longer drops non-standard ports from the |
W-22512224 |
||
Omni Gateway no longer returns |
W-24767532 |
||
The Health Check policy now reports violations as blocked requests, so they’re counted as policy violations and trigger the configured alerts. |
W-24513215 |
||
The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies no longer return a |
W-24279775 |
||
Omni Gateway no longer rejects valid requests when an API specification (OAS) uses a decimal |
W-24696857 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-24727246, W-24764986 |
October 23, 2026
MuleSoft announces the release of Omni Gateway 1.13.8.
Custom PDK policies can now access an API instance’s configured consumer URL through api.consumerUri in API Context.
| Issue Resolution | ID | ||
|---|---|---|---|
Omni Gateway now rejects certificates chaining through known compromised eMudhra intermediate certificates. |
W-24628768 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-24624014 |
October 21, 2026
MuleSoft announces the release of Omni Gateway 1.13.7.
Envoy is now upgraded to version 1.37.8.
The Credential Injection API Key policy now supports DataWeave expressions to resolve the API key from request attributes or payloads at runtime.
| Issue Resolution | ID | |
|---|---|---|
Path normalization is now disabled by default. To enable it, set |
W-24443266 |
|
Omni Gateway now uses |
W-24279051 |
|
Helm-generated inbound TLS bindings now apply the correct TLS-context precedence when APIs share a listener. |
W-24511699 |
|
Omni Gateway no longer crashes during startup in disconnected Runtime Fabric deployments when platform logging, monitoring, or metering endpoints are unavailable. |
W-24525793 |
|
The Header Injection policy no longer crashes Omni Gateway when a DataWeave string literal contains Unicode characters outside the Latin-1 range on AMD64 and ARM64 platforms. |
W-24090265 |
|
The JWT Validation, OpenID Connect OAuth 2.0 Token Enforcement, and OAuth 2.0 Token Introspection policies now preserve path segments and trailing slashes from consumer URLs when generating protected resource metadata URLs. |
W-24119444 |
|
The Injection Protection policy no longer incorrectly rejects legitimate multipart SOAP requests with binary attachments when body scanning is enabled. |
W-24361237 |
|
The JWT Validation policy now accepts RSA keys with padded base64url parameters in JWKS responses. |
W-24309516 |
|
Control-node replicas now retry concurrent revision updates with backoff instead of failing deployments with a precondition error. |
W-24580345 |
|
Omni Gateway now preserves component output during shutdown and no longer waits indefinitely when a descendant process keeps output streams open. |
W-24129984, W-24141774 |
|
These vulnerabilities detected by scanners are now fixed:
|
W-24456219, W-24578725 |
September 24, 2026
MuleSoft announces the release of Omni Gateway 1.13.6.
| Issue Resolution | ID | ||
|---|---|---|---|
Updating |
W-23969934 |
||
Configuration caching (control node) reliability is improved, including Redis recovery, deployment status, and configuration synchronization. |
W-22456427 |
||
The |
W-24062935 |
||
Log records larger than 32 KB no longer split into separate lines that lose their logging metadata. Oversized records are truncated instead. |
W-24055090 |
||
Omni Gateway running in Connected Mode no longer sends duplicate runtime logs to Anypoint Platform after logging configuration changes. |
W-24037601 |
||
Managed Omni Gateway deployments on Runtime Fabric no longer fail when the same image pull secret is supplied twice. |
W-24195540 |
||
The OpenID Connect OAuth 2.0 Token Enforcement policy now correctly applies |
W-24268807 |
||
The Basic Authentication: LDAP policy no longer includes sensitive authentication data in logs. |
W-24118398 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-24126253, W-24267883 |
August 27, 2026
MuleSoft announces the release of Omni Gateway 1.13.5.
| Issue Resolution | ID | ||
|---|---|---|---|
Omni Gateway running in Connected Mode no longer disconnects unexpectedly from Anypoint Platform under high-traffic conditions or when the remote server sends data without replying with protocol-level pong frames. |
W-23560278 |
||
Custom policies no longer crash Omni Gateway with a segmentation fault when a response payload is larger than the buffer limit (1 MB by default). Use the |
W-23692178 |
||
The Basic Authentication: LDAP policy no longer lets specially crafted usernames to manipulate the underlying LDAP search filter. |
W-23573199 |
||
Resetting Redis shared storage no longer fails with a cross-slot error in cluster-mode deployments (such as AWS ElastiCache). |
W-23687400 |
||
Control node no longer discards synchronization state after 14 days to prevent inconsistencies when a gateway reconnects following an extended outage. If you upgrade from an earlier version, see Configuration Caching (Control Node) Store Expiration After Upgrade. |
W-23692384 |
||
Control node Redis shared storage no longer grows without bound over time from historical configuration-change data. |
W-23748466 |
||
Omni Gateway running in Connected Mode no longer disrupts running pods when its registration credentials are renewed. |
W-23820257 |
||
Control node no longer delays propagating a configuration update or logs a false inconsistency warning after a transient failure while committing that update. |
W-23754016 |
||
Control node no longer fails to apply deployment updates when multiple replicas write to the same resource at nearly the same time. |
W-23748463, W-23748465 |
||
Custom policies no longer cause a memory leak that can increase memory usage over time. |
W-23941703 |
||
Omni Gateway no longer produces a malformed path predicate (such as a duplicate or missing slash) when a negative-lookahead path pattern is combined with an API base path. |
W-23912976 |
||
Omni Gateway running in Connected Mode no longer sends duplicate deployment-status updates to Anypoint Platform. |
W-23862236 |
||
The JWT Validation policy no longer bypasses the configured forward proxy when fetching JWKS keys. |
W-23840697 |
||
The Credential Injection OAuth 2.0 policy no longer ignores the configured caching duration when the OAuth 2.0 provider’s token response omits the token expiration value. |
W-23705875 |
||
The Rate Limiting SLA policy with distributed rate limiting enabled no longer crashes the gateway (WASM trap, returning a 503 error instead of 429) under Redis latency and high concurrency on the same SLA tier. |
W-23652660 |
||
The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies no longer forward the raw error response from the introspection server to the client. |
W-23665332 |
||
The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies no longer return a 503 error on all requests when the |
W-23940967 |
||
The OAuth 2.0 Token Introspection policy no longer fails when the introspection URL includes an explicit default port. |
W-23471294 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-23490974, W-23559915, W-23735964, W-23862957 |
July 23, 2026
MuleSoft announces the release of Omni Gateway 1.13.4.
| Issue Resolution | ID | ||
|---|---|---|---|
Policy initialization during Envoy configuration generation is now faster. Wasm module inspection and compilation are now cached across policies that share the same module. |
W-23480384 |
||
Configuration caching (control node) now works with AWS ElastiCache Serverless. Redis shared storage now uses the non-blocking |
W-23399906 |
||
The SOAP Validation policy no longer leaks temporary directories during configuration delivery. It now loads schema files whose paths contain spaces. |
W-23442789 |
||
The contract collector now honors the |
W-23460693 |
||
The JSON Threat Protection policy now accepts valid JSON containing an escaped forward slash ( |
W-23510751 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-22698091 |
July 8, 2026
MuleSoft announces the release of Omni Gateway 1.13.3.
Envoy is now upgraded to version 1.37.5.
| Issue Resolution | ID | ||
|---|---|---|---|
Omni Replicas no longer fail to receive configuration updates in Connected Mode when the hostname changed. |
W-23123632 |
||
Omni Gateway now supports deployments in environments using non-standard IP address ranges (240.0.0.0/4). |
W-22771253 |
||
The handling of rate-limited responses when downloading API configurations is now improved to reduce failures during high-traffic periods. |
W-23202349 |
||
The readiness probe accuracy is now improved to ensure Omni Gateway only reports as ready when all API configurations are successfully loaded and available for processing traffic. Set |
W-23297348 |
||
The XML Threat Protection policy now correctly validates and processes XML payloads. |
W-18172654 |
||
SLA tier tracking across authentication policies (Client ID Enforcement, JWT Validation) and Rate Limiting SLA policy is now improved for better analytics and governance. |
W-22937088 |
||
The Injection Protection policy pattern matching is now improved for better threat detection accuracy. |
W-22693332 |
||
The SOAP Schema Validation policy now correctly processes requests containing nested XOP elements in MTOM payloads |
W-21779437 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-22698091 |
June 6, 2026
MuleSoft announces the release of Omni Gateway 1.13.2.
| Issue Resolution | ID | ||
|---|---|---|---|
Logging for the |
W-21615708 |
||
The |
W-22545512 |
||
The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies now properly populate the |
W-22696442 |
||
The Injection Protection Policy now allows you to apply a policy that uses only custom protections. |
W-22491337 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-22698091 |
May 20, 2026
MuleSoft announces the release of Omni Gateway 1.13.1.
| Issue Resolution | ID | ||
|---|---|---|---|
The OpenTelemetry Collector now correctly starts in environments (such as Google Cloud Run) that were previously failing. |
W-22419420 |
||
The configuration caching (control-node) temporal inconsistency in the watcher and notifier is now fixed. |
W-21484884 |
||
The |
W-22365034 |
||
Contract resiliency for PDK now improves resource usage. |
W-22048194 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-22478633, W-22478649, W-22478660, W-22478666, W-22478702, W-22509993, W-22509992, W-22477420, W-22477544, W-22509994, W-22509995 |
May 11, 2026
MuleSoft announces the release of Omni Gateway 1.13.0.
Flex Gateway is now named to Omni Gateway.
Currently, this is a non-breaking change and only cosmetically affects the UI and documentation. This change shouldn’t affect CI/CD pipelines. There are no changes to these areas:
Anypoint Platform CLI
Anypoint Platform APIs
Logging
Environment variables
Documentation URL links
MCP tool names
Omni Gateway now supports GraphQL APIs.
To add a GraphQL API to Omni Gateway, see Adding an Omni Gateway API Instance.
Omni Gateway now provides these policies to support GraphQL APIs:
GraphQL Schema Validation: Validates incoming GraphQL operations against a GraphQL schema definition
GraphQL Introspection Control: Blocks or allows requests that access the schema, type, and __typename GraphQL meta fields
GraphQL Operation Limits: Limits GraphQL operation depth, aliases, root fields, and directives
GraphQL Static Query Complexity: Calculates query complexity and blocks requests that exceed the defined budget
Omni Gateway now supports WebSocket APIs.
To add a WebSocket API to Omni Gateway, see Adding an Omni Gateway API Instance.
Omni Gateway now provides the WebSocket Connection Limit to limit the number of simultaneous WebSocket connections that each API instance allows.
Omni Gateway is now supported in CloudHub 2.0 shared spaces.
To deploy a gateway to a shared space, see Deploy a Managed Omni Gateway.
Managed Omni Gateways deployed to CloudHub 2.0 private spaces now provide the Cluster endpoint for traffic internal to the cluster to bypass the CloudHub 2.0 ingress.
MCP Bridge now provides an improved creation experience.
Omni Gateway now supports conditional policy application for inbound policies to apply policies to specific methods, URI paths, hosts, and headers. Outbound policies support conditional policy application for specific methods and headers.
Envoy is now upgrade to version 1.37.2.
| Issue Resolution | ID |
|---|---|
Contracts are no longer dropped when the client secret is null. |
W-21177259 |
The OAuth 2.0 Token Introspection policy now correctly retrieves contracts when |
W-21371313 |
Readiness signal errors in the OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies are now fixed. |
W-21526778 |
When |
W-22300290 |
CORS policy now supports wildcard (*) origins. |
W-19971117 |
November 17, 2026
MuleSoft announces the release of Omni Gateway 1.12.13.
You can now configure the Redis shared storage timeout and number of retries with the new optional timeoutMilliseconds and maxRetries fields in the sharedStorage.redis configuration resource. If you don’t set these fields, Omni Gateway uses a two-second timeout and one retry, instead of the previous five-second connect timeout, three-second read and write timeout, and three retries. To keep behavior similar to previous versions, set timeoutMilliseconds: 3000 and maxRetries: 3.
The Credential Injection API Key policy now supports removing specified headers, such as an existing Authorization header, from the request before injecting the credential.
The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies now receive the consumer URL for protected resource metadata from the API instance’s configuration, so they no longer need to retrieve it from Anypoint API Manager.
Envoy is now upgraded to version 1.35.13.
The OpenTelemetry Collector is now upgraded to version 0.164.0.
| Issue Resolution | ID | ||
|---|---|---|---|
Omni Gateway no longer drops non-standard ports from the |
W-22512224 |
||
Omni Gateway no longer returns |
W-24767532 |
||
The Health Check policy now reports violations as blocked requests, so they’re counted as policy violations and trigger the configured alerts. |
W-24513215 |
||
The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies no longer return a |
W-24279775 |
||
Omni Gateway no longer rejects valid requests when an API specification (OAS) uses a decimal |
W-24696857 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-24727246, W-24749333, W-24764986 |
October 23, 2026
MuleSoft announces the release of Omni Gateway 1.12.12.
Custom PDK policies can now access an API instance’s configured consumer URL through api.consumerUri in API Context.
| Issue Resolution | ID | ||
|---|---|---|---|
Omni Gateway now rejects certificates chaining through known compromised eMudhra intermediate certificates. |
W-24628768 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-24624014 |
October 21, 2026
MuleSoft announces the release of Omni Gateway 1.12.11.
The Credential Injection API Key policy now supports DataWeave expressions to resolve the API key from request attributes or payloads at runtime.
| Issue Resolution | ID |
|---|---|
Path normalization is now disabled by default. To enable it, set |
W-24443266 |
Omni Gateway now uses |
W-24279051 |
Helm-generated inbound TLS bindings now apply the correct TLS-context precedence when APIs share a listener. |
W-24511699 |
Omni Gateway no longer crashes during startup in disconnected Runtime Fabric deployments when platform logging, monitoring, or metering endpoints are unavailable. |
W-24525793 |
The Header Injection policy no longer crashes Omni Gateway when a DataWeave string literal contains Unicode characters outside the Latin-1 range on AMD64 and ARM64 platforms. |
W-24090265 |
Control-node replicas now retry concurrent revision updates with backoff instead of failing deployments with a precondition error. |
W-24580345 |
Omni Gateway now preserves component output during shutdown and no longer waits indefinitely when a descendant process keeps output streams open. |
W-24129984, W-24141774 |
September 25, 2026
MuleSoft announces the release of Omni Gateway 1.12.10.
| Issue Resolution | ID | ||
|---|---|---|---|
Configuration caching (control node) reliability is improved, including Redis recovery, deployment status, and configuration synchronization. |
W-22456427 |
||
The |
W-24062935 |
||
Omni Gateway no longer splits log entries longer than 8 KB into continuation lines that can be misclassified. Lines up to 32 KB are preserved, and longer lines are truncated and marked. |
W-24055090 |
||
Managed Omni Gateway deployments on Runtime Fabric no longer fail when the same image pull secret is supplied by both Gateway Manager and Runtime Fabric. |
W-24195540 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-24126253, W-24267883 |
August 27, 2026
MuleSoft announces the release of Omni Gateway 1.12.9.
The OpenTelemetry Collector is now upgraded to version 0.158.0.
| Issue Resolution | ID | ||
|---|---|---|---|
Omni Gateway running in Connected Mode no longer disconnects unexpectedly from Anypoint Platform under high-traffic conditions or when the remote server sends data without replying with protocol-level pong frames. |
W-23560278 |
||
Custom policies no longer crash Omni Gateway with a segmentation fault when a response payload is larger than the buffer limit (1 MB by default). Use the |
W-23692178 |
||
The Basic Authentication: LDAP policy no longer lets specially crafted usernames to manipulate the underlying LDAP search filter. |
W-23573199 |
||
Resetting Redis shared storage no longer fails with a cross-slot error in cluster-mode deployments (such as AWS ElastiCache). |
W-23687400 |
||
Control node no longer discards synchronization state after 14 days to prevent inconsistencies when a gateway reconnects following an extended outage. If you upgrade from an earlier version, see Configuration Caching (Control Node) Store Expiration After Upgrade. |
W-23692384 |
||
Control node Redis shared storage no longer grows without bound over time from historical configuration-change data. |
W-23748466 |
||
The configuration caching (control-node) temporal inconsistency in the watcher and notifier is now fixed. |
W-21764662 |
||
Omni Gateway running in Connected Mode no longer disrupts running pods when its registration credentials are renewed. |
W-23820257 |
||
Control node no longer delays propagating a configuration update or logs a false inconsistency warning after a transient failure while committing that update. |
W-23754016 |
||
Control node no longer fails to apply deployment updates when multiple replicas write to the same resource at nearly the same time. |
W-23748463, W-23748465 |
||
Custom policies no longer cause a memory leak that can increase memory usage over time. |
W-23941703 |
||
Omni Gateway no longer produces a malformed path predicate (such as a duplicate or missing slash) when a negative-lookahead path pattern is combined with an API base path. |
W-23912976 |
||
The Credential Injection OAuth 2.0 policy no longer ignores the configured caching duration when the OAuth 2.0 provider’s token response omits the token expiration value. |
W-23705875 |
||
The Rate Limiting SLA policy with distributed rate limiting enabled no longer crashes the gateway (WASM trap, returning a 503 error instead of 429) under Redis latency and high concurrency on the same SLA tier. |
W-23652660 |
||
The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies no longer forward the raw error response from the introspection server to the client. |
W-23665332 |
||
The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies no longer return a 503 error on all requests when the |
W-23940967 |
||
The contract collector now honors the |
W-23460693 |
||
The OAuth 2.0 Token Introspection policy no longer fails when the introspection URL includes an explicit default port. |
W-23471294 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-23490974, W-23559915, W-23862957 |
July 21, 2026
MuleSoft announces the release of Omni Gateway 1.12.8.
| Issue Resolution | ID | ||
|---|---|---|---|
Omni Replicas no longer fail to receive configuration updates in Connected Mode when the hostname changed. |
W-23123632 |
||
Omni Gateway now supports deployments in environments using non-standard IP address ranges (240.0.0.0/4). |
W-22771253 |
||
The handling of rate-limited responses when downloading API configurations is now improved to reduce failures during high-traffic periods. |
W-23202349 |
||
The readiness probe accuracy is now improved to ensure Omni Gateway only reports as ready when all API configurations are successfully loaded and available for processing traffic. Set |
W-23297348 |
||
The XML Threat Protection policy now correctly validates and processes XML payloads. |
W-18172654 |
||
The Injection Protection policy pattern matching is now improved for better threat detection accuracy. |
W-22693332 |
||
HTTP retry logic now drains response bodies between retry attempts to prevent connection pool exhaustion. |
W-23252601 |
||
Configuration caching (control node) now works with AWS ElastiCache Serverless. Redis shared storage now uses the non-blocking |
W-23399906 |
||
Policy initialization during Envoy configuration generation is now faster. Wasm module inspection and compilation are now cached across policies that share the same module. |
W-23480384 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-22698091 |
June 6, 2026
MuleSoft announces the release of Anypoint Omni Gateway 1.12.7.
| Issue Resolution | ID | ||
|---|---|---|---|
The principal is no longer always null in the authentication object for OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies. |
W-22696442 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-22698091 |
May 20, 2026
MuleSoft announces the release of Anypoint Flex Gateway 1.12.6.
| Issue Resolution | ID | ||
|---|---|---|---|
The OpenTelemetry Collector now correctly starts in environments (such as Google Cloud Run) that were previously failing. |
W-22419420 |
||
The configuration caching (control-node) temporal inconsistency in the watcher and notifier is now fixed. |
W-21484884 |
||
The |
W-22365034 |
||
The Injection Protection Policy now allows you to apply a policy that only uses custom protections. |
W-22491337 |
||
Contract resiliency for PDK now improves resource usage. |
W-22048194 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-22478633, W-22478649, W-22478660, W-22478666, W-22478702, W-22509993, W-22509992, W-22477420, W-22477544, W-22509994, W-22509995 |
May 7, 2026
MuleSoft announces the release of Anypoint Flex Gateway 1.12.5.
| Issue Resolution | ID |
|---|---|
MCP and A2A metrics are now reported correctly. |
W-22346105 |
The OAuth 2.0 Token Introspection and OpenID Connect OAuth 2.0 Token Enforcement policies now correctly use the consumer URL for protected resource metadata. |
W-22215222 |
April 29, 2026
MuleSoft announces the release of Anypoint Flex Gateway 1.12.4.
Envoy is now updated to version 1.35.10.
| Issue Resolution | ID |
|---|---|
Vulnerabilities detected by scanners are now fixed. |
W-22139443 |
April 22, 2026
MuleSoft announces the release of Anypoint Flex Gateway 1.12.3.
| Issue Resolution | ID |
|---|---|
Vulnerabilities detected by scanners are now fixed. |
W-22028896 |
The DataWeave |
W-21643871 |
The OpenID Policy now correctly sends identity provider credentials in the header instead of the body. |
W-22061343 |
Rate Limiting policies now correctly distribute the quota between replicas when distributed rate-limiting is enabled. |
W-22108203 |
March 31, 2026
MuleSoft announces the release of Anypoint Flex Gateway 1.12.2.
The OAuth 2.0 Token Introspection Policy and OpenID Connect OAuth 2.0 Token Enforcement Policy now support the OAuth 2.0 discovery flow and parameters required for MCP clients.
| Issue Resolution | ID |
|---|---|
Vulnerabilities detected by scanners are now fixed. |
W-21668427 |
When making outbound requests from policies, the port is no longer included in the request authority unless the port is explicitly specified in the target URL. |
W-21471214 |
March 2, 2026
MuleSoft announces the release of Anypoint Flex Gateway 1.12.1.
| Issue Resolution | ID |
|---|---|
Managed Flex Gateway deployed on CloudHub 2.0 no longer produces UDP log errors. |
W-21361063 |
February 25, 2026
MuleSoft announces the release of Anypoint Flex Gateway 1.12.0.
Managed Flex Gateway now supports Runtime Fabric deployments.
Extra Large Managed Flex Gateway is now available for production purposes with higher throughput and more process demanding policies.
To learn more about the performance metrics for Extra Large Managed Flex Gateway, see Managed Flex Gateway Limits and Performance Metrics.
Flex Gateway now supports creating an MCP Bridge to expose API instances as an MCP server.
These DataWeave policies are added to modify and filter requests:
DataWeave Body Transformation Policy: Transforms request or response body content with a DataWeave script
DataWeave Headers Transformation Policy: Transforms request or response headers with a DataWeave script
DataWeave Request Filter Policy: Filters requests by using a DataWeave script
A Credential Injection JWT Generation policy is added to generate and inject JWT tokens into outgoing requests.
A Injection Protection policy is added to scan incoming request headers, path, query string, and body for SQL injection, XSS (Cross-Site Scripting), and custom injection attacks.
Functionality is added to configure TLS for outgoing HTTP requests from Self-Managed Flex Gateway policies.
Managed Flex Gateway and Self-Managed Flex Gateway running in Connected Mode now provides the Runtime Configuration tab in Runtime Manager to configure and edit logging, tracing, timeouts, circuit breakers, probes, and other runtime properties.
SOAP APIs now support Payloads over 1MB.
Managed Flex Gateway replicas now communicate directly with each other for real-time sharing of HTTP caching and rate limiting data instead of using Object Storage V2.
Flex Gateway now supports dw::Core::-- DataWeave functions.
See -- Functions.
| Issue Resolution | ID |
|---|---|
The SOAP Schema Validation Policy no longer intermittently bypasses validation |
W-20173820 |
Flex Gateway no longer has a usage mismatch when using an HTTP probe. |
W-20278837 |
Flex Gateway now retries to download contracts from Anypoint Platform after failure. |
W-20435629 |
Flex Gateway no longer has temporary request failures during API specification (OAS) updates. |
W-20646216 |
JSON Threat Protection Policy no longer rejects numeric exponential notation. |
W-21186984 |
Vulnerabilities detected by scanners are now fixed. |
W-21188054 |
Flex Gateway no longer loses metric data when A2A and MCP policies are applied. |
W-21016899 |
November 17, 2026
MuleSoft announces the release of Omni Gateway 1.9.20.
| Issue Resolution | ID | ||
|---|---|---|---|
Omni Gateway no longer drops non-standard ports from the |
W-22512224 |
||
The Health Check policy now reports violations as blocked requests, so they’re counted as policy violations and trigger the configured alerts. |
W-24513215 |
||
The OpenID Connect OAuth 2.0 Token Enforcement and OAuth 2.0 Token Introspection policies no longer return a |
W-24279775 |
||
Omni Gateway no longer rejects valid requests when an API specification (OAS) uses a decimal |
W-24696857 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-24764986, W-24765178 |
October 23, 2026
MuleSoft announces the release of Omni Gateway 1.9.19.
| Issue Resolution | ID | ||
|---|---|---|---|
Omni Gateway now rejects certificates chaining through known compromised eMudhra intermediate certificates. |
W-24628768 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-24624014 |
October 21, 2026
MuleSoft announces the release of Omni Gateway 1.9.18.
| Issue Resolution | ID | |
|---|---|---|
Path normalization is now disabled by default. To enable it, set |
W-24443266 |
|
Omni Gateway now uses |
W-24279051 |
|
Helm-generated inbound TLS bindings now apply the correct TLS-context precedence when APIs share a listener. |
W-24511699 |
|
The Header Injection policy no longer crashes Omni Gateway when a DataWeave string literal contains Unicode characters outside the Latin-1 range on AMD64 and ARM64 platforms. |
W-24090265 |
|
Control-node replicas now retry concurrent revision updates with backoff instead of failing deployments with a precondition error. |
W-24580345 |
|
These vulnerabilities detected by scanners are now fixed:
|
W-24578725 |
September 24, 2026
MuleSoft announces the release of Omni Gateway 1.9.17.
| Issue Resolution | ID |
|---|---|
Updating |
W-23969934 |
Configuration caching (control node) reliability is improved, including Redis recovery, deployment status, and configuration synchronization. |
W-22456427 |
The |
W-24062935 |
Managed Omni Gateway deployments on Runtime Fabric no longer fail when the same image pull secret is supplied by both Gateway Manager and Runtime Fabric. |
W-24195540 |
August 27, 2026
MuleSoft announces the release of Omni Gateway 1.9.16.
| Issue Resolution | ID | ||
|---|---|---|---|
The Basic Authentication: LDAP policy no longer lets specially crafted usernames to manipulate the underlying LDAP search filter. |
W-23573199 |
||
Resetting Redis shared storage no longer fails with a cross-slot error in cluster-mode deployments (such as AWS ElastiCache). |
W-23687400 |
||
Control node no longer discards synchronization state after 14 days to prevent inconsistencies when a gateway reconnects following an extended outage. If you upgrade from an earlier version, see Configuration Caching (Control Node) Store Expiration After Upgrade. |
W-23692384 |
||
The configuration caching (control-node) temporal inconsistency in the watcher and notifier is now fixed. |
W-21764662 |
||
Configuration caching (control node) now works with AWS ElastiCache Serverless. Redis shared storage now uses the non-blocking |
W-23399906 |
||
Control node Redis shared storage no longer grows without bound over time from historical configuration-change data. |
W-23748466 |
||
Control node no longer fails to apply deployment updates when multiple replicas write to the same resource at nearly the same time. |
W-23748463, W-23748465 |
||
Control node no longer delays propagating a configuration update or logs a false inconsistency warning after a transient failure while committing that update. |
W-23754016 |
||
Omni Gateway running in Connected Mode no longer disrupts running pods when its registration credentials are renewed. |
W-23820257 |
||
The contract collector now honors the |
W-23460693 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-23559915, W-23735964, W-23862957 |
July 21, 2026
MuleSoft announces the release of Omni Gateway 1.9.15.
| Issue Resolution | ID | ||
|---|---|---|---|
Omni Replicas no longer fail to receive configuration updates in Connected Mode when the hostname changed. |
W-23123632 |
||
HTTP retry logic now drains response bodies between retry attempts to prevent connection pool exhaustion. |
W-23252601 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-22698091 |
June 6, 2026
MuleSoft announces the release of Anypoint Omni Gateway 1.9.14.
| Issue Resolution | ID | ||
|---|---|---|---|
These vulnerabilities detected by scanners are now fixed:
|
W-22698091 |
May 20, 2026
MuleSoft announces the release of Anypoint Flex Gateway 1.9.13.
| Issue Resolution | ID | ||
|---|---|---|---|
The |
W-22365034 |
||
These vulnerabilities detected by scanners are now fixed:
|
W-22478633, W-22478649, W-22478660, W-22478666, W-22478702, W-22509993, W-22509992 |
April 24, 2026
MuleSoft announces the release of Anypoint Flex Gateway 1.9.12.
| Issue Resolution | ID |
|---|---|
Vulnerabilities detected by scanners are now fixed. |
W-22028896 |
March 31, 2026
MuleSoft announces the release of Anypoint Flex Gateway 1.9.11.
| Issue Resolution | ID |
|---|---|
Vulnerabilities detected by scanners are now fixed. |
W-21668427 |
March 5, 2026
MuleSoft announces the release of Anypoint Flex Gateway 1.9.10.
| Issue Resolution | ID |
|---|---|
Vulnerabilities detected by scanners are now fixed. |
W-21259850 |
Trace configuration now supports setting up a trusted CA. |
W-21018187 |
The JSON Threat Protection policy no longer rejects numeric exponential notation. |
W-21186984 |
The Schema Validation policy now validates the raw URL-encoded raw value instead of the URL-decoded value. |
W-20531156 |
Flex Gateway no longer loses metric data when A2A and MCP policies are applied. |
W-21016899 |
January 7, 2026
MuleSoft announces the release of Anypoint Flex Gateway 1.9.9.
| Issue Resolution | ID |
|---|---|
Vulnerabilities detected by scanners are now fixed. |
W-20365927 |
If an error occurs when the JWT Validation policy calls the JWKS server, the time between retry requests now doubles with each request. |
W-19647107 |
Flex Gateway now correctly sends logging information to Anypoint Platform. |
W-20365743 |
November 13, 2025
MuleSoft announces the release of Anypoint Flex Gateway 1.9.8.
| Issue Resolution | ID |
|---|---|
Flex Gateway running in Connected Mode now retries when requests to Anypoint Platform fail. |
W-20037629 |
Vulnerabilities detected by scanners are now fixed. |
W-20125828 |
October 17, 2025
MuleSoft announces the release of Anypoint Flex Gateway 1.9.7.
For the Rate Limiting and SLA-Based Rate Limiting policies, if distributed rate limiting is enabled, the policy resizes time windows under 10 seconds linearly. For example, if you configure a max of 10 requests per 5 seconds, the policy resizes that window to a max of 20 requests per 10 seconds.
| Issue Resolution | ID |
|---|---|
Flex Gateway registration calls from Docker no longer fail for Hyperforce deployments. |
W-19444135 |
Vulnerabilities detected by scanners are now fixed. |
W-19787132, W-19971092 |
The Connected Mode deployment process is now improved. |
W-19861373 |
August 26, 2025
MuleSoft announces the release of Anypoint Flex Gateway 1.9.6.
| Issue Resolution | ID |
|---|---|
OAS Schemas are now correctly present in the local configuration cache. |
W-18833198 |
The Envoy agent now properly restarts child processes that end with a core dump or kill signal. |
W-19327530 |
The readiness probe no longer fails when the OAuth Token Introspection policy has |
W-19118057 |
The readiness probe no longer fails when the OpenID Connect OAuth 2.0 Token Enforcement policy has |
W-19304854 |
Vulnerabilities detected by scanners are now fixed. |
W-19095531, W-19308177 |
Flex Gateway now validates that there are no collisions when an API base path uses regex expressions. |
W-19149269 |
July 2, 2025
MuleSoft announces the release of Anypoint Flex Gateway 1.9.5.
Fluent Bit is now updated to version 3.2.10.
| Issue Resolution | ID |
|---|---|
Flex Gateway no longer ignores the |
W-18465012 |
Vulnerabilities detected by scanners are now fixed. |
W-18820570 |
The Credential Injection OAuth 2.0 policy no longer fails if the |
W-18779819 |
The Schema Validation policy now recognizes encoded query params correctly. |
W-18883397 |
June 4, 2025
MuleSoft announces the release of Anypoint Flex Gateway 1.9.4.
| Issue Resolution | ID |
|---|---|
Deploying Flex Gateway with IPv6 disabled no longer causes an error. |
W-18671361 |
May 28, 2025
MuleSoft announces the release of Anypoint Flex Gateway 1.9.3.
Flex Gateway now supports the Model Context Protocol (MCP) and the Agent2Agent (A2A) Protocol, enabling you to secure, manage, and govern agent interactions:
You can Publish Flex Gateway MCP and A2A Server instances.
Flex Gateway now includes MCP and A2A policies. Using these new policies, you can:
Protect agent interactions: Require that agents are invoked with appropriate authentication and authorization.
Enhance agent requests: Modify incoming prompts with additional context to improve server agent execution.
Provide centralized oversight: Enable frictionless agent visibility, logging, and insights for debugging and optimization.
Secure connections: Restrict MCP endpoint access to authorized agents only.
Simplify governance: Provide centralized visibility and control over all interactions.
Flex Gateway now includes these policies:
A2A Policies:
A2A Schema Validation: Verify requests conform to the A2A schema.
See A2A Schema Validation Policy.
A2A Agent Card: Proxy the agent through Flex Gateway by rewriting the agent card.
See A2A Agent Card Policy
A2A PII Detector: Detect sensitive information in messages sent to and from agents.
See A2A Personally Identifiable Information (PII) Detector Policy.
A2A Prompt Decorator: Modify prompt behavior by injecting custom prompts into requests.
See A2A Prompt Decorator Policy.
Server-Sent Events (SSE) Content Logging: Log content sent by agents for audit and compliance needs.
See SSE Logging Policy.
MCP Policies:
MCP Schema Validation: Verify requests conform to the MCP schema.
See MCP Schema Validation Policy.
MCP Support: Enable MCP support and enable Server-Sent Events (SSE).
See MCP Support Policy.
MCP Attribute-Based Access Control: Allows you to control access to tools, resources, and prompts, based on Cedar expressions.
See MCP Attribute-Based Access Control Policy.
To learn more, see:
May 12, 2025
MuleSoft announces the release of Anypoint Flex Gateway 1.9.2.
| Issue Resolution | ID |
|---|---|
The Flex Gateway 1.9.1 TLS context configuration deployment regression is now fixed. |
W-18483362 |
May 8, 2025
MuleSoft announces the release of Anypoint Flex Gateway 1.9.1.
| Issue Resolution | ID |
|---|---|
The |
W-18368903 |
The Flex Gateway 1.9.0 ForwardProxy regression is now fixed. |
W-18202000 |
The |
W-18201673 |
Redis keys no longer collide if multiple Flex Gateways use the same Redis server. |
W-18004157 |
Redeploying one API instance after updating a TLS Context now updates the context for APIs that share the TLS context. |
W-17737710 |
March 18, 2025
MuleSoft announces the release of Anypoint Flex Gateway 1.9.0.
Managed Flex Gateway on CloudHub 2.0
Flex Gateway now includes Managed Flex Gateway, a fully hosted version of Flex Gateway on CloudHub 2.0. Managed Flex Gateway provides high availability, autoscaling, less operational overhead, and regular automatic patches and upgrades.
Note: To use Managed Flex Gateway, ensure the business group you want to deploy your gateway to has Managed Flex Gateway Resources.
Flex Gateway Version Lifecycle
MuleSoft introduces two new release channels, Edge and Long-term Support (LTS). Both release channels are available in all deployment models: Managed Flex Gateway, Self-Managed Flex Gateway Connected Mode, and Self-Managed Flex Gateway Local Mode. Edge releases will be available three times per year, and LTS releases will be available once a year.
Outbound Policy Support
Outbound policies are policies applied to specific upstreams. To find the new outbound policies, see Outbound Policies Directory.
To apply outbound policies with UI, see Applying Policies for Managed Omni Gateways and Connected Mode. To apply a policy to a service in Local Mode, see Secure an API with an Automated Resource-Level Policy.
Flex Local Configuration Cache
Flex Gateway running in Connected mode can now cache its gateway configuration in shared storage for faster replica initiation, reduced startup times, and accelerated autoscaling.
Flex Scalability
Flex Gateway now supports up to 1,000 APIs per gateway.
API Timeouts
Flex Gateway now provides the Stream Idle timeout, Response timeout, and Upstream Idle timeout. You can apply the timeouts to the gateway or individual APIs and upstreams as policies. To learn more, see:
| Issue Resolution | ID |
|---|---|
When deployed to a Virtual Machine (VM), a Self-Managed Flex Gateway no longer fails to restart after an abrupt stop of the VM. |
W-17640917 |
The Flex Gateway is unable to send logs when a forward proxy is enabled known issue was introduced in Flex Gateway 1.9.0.
For more information, see Salesforce Known Issues and set the category to Mulesoft Flex Gateway.