What's new in Traefik Hub?
November 2025
What's New
Traefik Hub v3.19 with Traefik Proxy v3.6
Traefik Hub v3.19 ships with Traefik Proxy v3.6, introducing powerful new routing capabilities and serverless integration:
-
Multi-Layer Routing: Advanced HTTP routing that enables sophisticated traffic management through prioritized route evaluation. Routes are now evaluated in sequence according to explicit priorities, allowing you to create complex routing strategies, such as API versioning, gradual rollouts, and conditional routing based on headers, paths, or query parameters (among others). This feature provides fine-grained control over request flow, enabling patterns such as blue-green deployments and sophisticated A/B testing. See the Multi-Layer Routing documentation for configuration details.
-
Knative Provider: Native integration with Knative Serving enables Traefik Hub to act as the networking layer for serverless workloads. This provider brings together Traefik's advanced routing capabilities with Knative's scale-to-zero architecture, supporting tag-based routing for A/B testing, percentage-based traffic splitting for canary deployments, and automatic service discovery. Traefik Hub becomes the only proxy that can seamlessly operate across cloud-native containers, traditional VMs, and serverless workloads in a unified deployment. See the Knative provider installation and routing configuration documentation.
-
Gateway API v1.4.0: Updated support for the latest Kubernetes Gateway API specification, bringing enhanced routing capabilities and improved conformance with the Gateway API standard.
LDAP Authentication for API Management
Traefik Hub API Management now supports LDAP (Lightweight Directory Access Protocol) authentication for both API Portal and API access. Organizations can leverage their existing LDAP infrastructure, including OpenLDAP, Active Directory, and Oracle Internet Directory, to authenticate users and applications without requiring additional identity providers.
LDAP Portal Authentication enables portal users to authenticate with their LDAP credentials through an interactive login form. User attributes (email, name) and group memberships are automatically synchronized from LDAP in online mode, providing seamless integration with existing directory services. Portal access can be controlled using LDAP group membership, making it easy to grant developers access based on their organizational roles.
LDAP API Authentication validates API requests using HTTP Basic Authentication with LDAP credentials. Each request is authenticated against the LDAP server, with the LDAP username matching the appId in a ManagedApplication resource. This stateless authentication method works with both ManagedSubscriptions for access control and APIPlans for rate limiting, providing the same governance capabilities as API Key and JWT authentication.
Key features include:
- Dual authentication modes: Portal authentication with interactive login forms and API authentication with per-request Basic Auth
- Multiple LDAP providers: Supports OpenLDAP, Active Directory, and Oracle Internet Directory
- Group-based access control: LDAP groups (via
memberOfattribute) control portal visibility and API access - Flexible deployment: Works in both online mode (with attribute sync) and offline mode (authentication only)
- Security options: LDAPS, StartTLS, and custom CA certificate support
- Configurable bucket strategies: Rate limits and quotas can be scoped per subscription, per application, or per application-API pair using the new
bucketfield inAPIPlan - UI and CRD configuration: Configure LDAP through the Traefik Hub Dashboard or using
APIPortalAuthandAPIAuthCRDs
For complete configuration details, see the LDAP Authentication , APIPlan, APIPortalAuth, and APIAuth documentation.
Artifactory Support for Private Plugins (Early-Access)
Traefik Hub API Gateway now supports loading plugins from Artifactory repositories configured as VCS mirrors (GitHub, Bitbucket, etc.). This feature enables organizations to use proprietary or internal plugins while maintaining security through token-based authentication and hash verification.
For more details, see the Private Plugins documentation and plugin development guide.
Multi-Issuer JWT Support
The JWT middleware now supports multiple trusted issuers through the new trustedIssuers option. This enables applications to accept JWTs from multiple identity providers simultaneously, with each issuer configured with its own JWKS endpoint and optional issuer validation. The feature supports both strict issuer matching and fallback scenarios for flexible multi-provider authentication. See the JWT middleware documentation for configuration details.
Compatibility Matrix
This release comes with the following components:
| Component | Version |
|---|---|
| Traefik Hub | v3.19.0-ea.9 |
| Helm Chart | v37.4.0 |
| Traefik Proxy | v3.6.2 |
| Coraza WAF | v3.3.3 |
| OWASP CRS | v4.14.0 |
| Static Analyzer | v1.5.0 |
| Kubernetes Gateway API | v1.4.0 |
October 2025
What's New
Private Plugins Support
Traefik Hub API Gateway now supports loading plugins from private GitHub and GitLab repositories. This feature enables organizations to use proprietary or internal plugins while maintaining security through token-based authentication and hash verification.
Key capabilities include:
- Private GitHub repositories: Support for GitHub.com, GitHub Enterprise Cloud, and GitHub Enterprise Server
- Private GitLab repositories: Support for GitLab.com and self-hosted GitLab instances
- Secure authentication: Token-based access using personal access tokens or project tokens
- Hash verification: SHA-256 hash verification ensures plugin integrity and prevents tampering
- Kubernetes secret integration: Secure token storage using URN secret references
- Multiple registry sources: Configure multiple plugin sources from different Git providers
This feature is particularly valuable for enterprises that need to distribute internal plugins, maintain proprietary middleware, or ensure plugin security through controlled access and verification.
For more details, see the Private Plugins documentation.
MCP Gateway with Task-Based Access Control (Early-Access)
Traefik Hub now includes MCP Gateway, a dedicated gateway for securing and governing Model Context Protocol (MCP) servers. The MCP Gateway acts as an OAuth-compliant proxy that enables organizations to centrally manage access to MCP servers, tools, and resources with Task-Based Access Control (TBAC)—a new authorization paradigm designed specifically for AI agents.
Why TBAC? Traditional Role-Based Access Control (RBAC) fails for AI agents because agents don't have static job functions—they complete tasks that span multiple domains. TBAC provides authorization across three dimensions: Tasks (business objectives), Tools (system access), and Transactions (parameter-level constraints), ensuring agents get precisely the permissions they need for their current work, nothing more.
Variable Substitution. Traefik's ${jwt.claim} and ${mcp.parameter} syntax enables writing a single adaptive policy that works for unlimited agents, with permissions determined by JWT claims. Instead of managing thousands of agent-specific policy lines, you write a handful of policies that dynamically enforce authorization based on each agent's claims—making TBAC practical at enterprise scale.
The MCP Gateway includes:
- Task-Based Access Control (TBAC) with three-dimensional authorization (tasks, tools, transactions) using variable substitution for scalable, adaptive policies
- MCP middleware with expression language supporting string matching (Equals, Contains, Prefix) and numeric comparisons (Lt, Gt, Lte, Gte) for transaction-level limits like approval amounts and rate quotas
- OAuth 2.1/2.0 Resource Server compliance with automatic
/.well-known/oauth-protected-resourceendpoint generation for MCP client discovery - JWT authentication for seamless integration with existing identity providers (Auth0, Okta, Azure AD, etc.)
- Zero infrastructure overhead by leveraging existing identity providers—no new databases, policy engines, or specialized infrastructure required
- Sub-millisecond authorization through stateless JWT validation with no external API calls or database queries
- Comprehensive audit trails capturing the complete three-dimensional authorization context for compliance (SOX, HIPAA, GDPR, PCI DSS)
- OpenTelemetry observability with metrics and traces for all MCP operations
The MCP Gateway is essential for organizations deploying AI agents that need controlled access to external tools and data sources. Unlike traditional approaches that rely on role inheritance or impersonation, TBAC ensures AI systems get precisely scoped permissions based on the work they're performing.
To enable MCP Gateway, use:
--set hub.mcpgateway.enabled=true
For more details, see the MCP Gateway documentation, Understanding TBAC guide, and getting started guide.
Traefik Hub v3.18 with Traefik Proxy v3.5
Traefik Hub v3.18 now ships with Traefik Proxy v3.5, bringing several new features and improvements like:
-
Kubernetes Ingress NGINX Provider: Native support for NGINX-specific Ingress annotations, enabling seamless migration from NGINX Ingress Controller to Traefik Hub while preserving existing configurations. See the Kubernetes Ingress NGINX provider documentation and routing configuration guide.
-
OCSP Stapling: Online Certificate Status Protocol (OCSP) stapling support improves TLS handshake performance and enhances client privacy by providing certificate revocation status directly during the TLS handshake. Learn more in the OCSP Stapling documentation.
-
Configuration Terminology Update: To better reflect the purpose of each configuration type, we've renamed "Static Configuration" to "Install Configuration" and "Dynamic Configuration" to "Routing Configuration" throughout the documentation. This change provides clearer guidance on where different settings should be configured.
-
ACME Provider HTTP Timeout: The ACME provider now supports HTTP timeout with the
clientTimeoutandclientResponseHeaderTimeoutoptions, allowing you to configure the timeout for HTTP requests and response headers to the ACME server. See the ACME provider documentation for more details.
Compatibility Matrix
This release comes with the following components:
| Component | Version |
|---|---|
| Traefik Hub | v3.18.0 |
| Helm Chart | v37.2.0 |
| Traefik Proxy | v3.5.3 |
| Coraza WAF | v3.3.3 |
| OWASP CRS | v4.14.0 |
| Static Analyzer | v1.5.0 |
| Kubernetes Gateway API | v1.3.0 |
September 2025
What's New
New Middleware: LLM Guard (AI Gateway)
The LLM Guard middleware brings flexible content security to any API traffic through external guard services or LLMs. This middleware supports four variants to handle different integration patterns, from generic APIs with custom security services to chat completions with LLM-based guards like Llama Guard.
The non-chat-completion variants (llm-guard and llm-guard-custom) provide a unique advantage by applying AI-powered security analysis to any incoming API traffic, not just AI or chat APIs. The -custom suffix variants integrate with non-chat-compatible upstream guard services. While traditional solutions only secure predefined AI formats, Traefik Hub protects your entire API ecosystem including e-commerce product APIs, banking transactions, HR systems, and customer data endpoints. This enables AI-driven threat detection, content policy enforcement, and fraud analysis across all business APIs.
Key features include:
- Custom Go templates for request formatting
- Powerful JSON path expressions for blocking conditions
- Integration with safety models supporting categories like hate speech and violence detection
- Streaming response analysis for chat completions
- Full response body logging with the
logResponseBodyoption for debugging - Multi-layered security pipelines where multiple guards can analyze different aspects of interactions before they reach backend services
For complete configuration details and deployment patterns, see the LLM Guard middleware documentation.
August 2025
What's New
New Middleware: Force Case
The Force Case middleware enforces specific header casing for both incoming requests and outgoing responses. HTTP headers are typically case-insensitive according to RFC specifications, but some legacy systems or APIs require headers to maintain specific capitalization patterns.
This middleware ensures that designated headers preserve their exact case format instead of being normalized to canonical MIME header format. It's particularly useful for SOAP services that expect headers like SOAPAction with exact capitalization, legacy API integrations with strict header casing requirements, and compliance scenarios where specific header formatting must be preserved.
For more details, see the Force Case middleware documentation.
Compatibility Matrix
This release comes with the following components:
| Component | Version |
|---|---|
| Traefik Hub | v3.18.0-beta3 |
| Helm Chart | v37.0.0 |
| Traefik Proxy | v3.4.5 |
| Coraza WAF | v3.3.3 |
| OWASP CRS | v4.14.0 |
| Static Analyzer | v1.5.0 |
| Kubernetes Gateway API | v1.2.1 |
July 2025
What's New
API Management Offline Mode
Traefik Hub API Management now supports full offline operation, providing the same level of authentication and API management configuration as the Online Dashboard. This release introduces two new Custom Resource Definitions:
APIAuthfor namespace-level API authentication using API Key or JWTAPIPortalAuthfor configuring API Portal authentication with OpenID Connect (OIDC). The OIDC integration works with major identity providers such as Auth0, Azure AD, and Keycloak and includes flexible claim mapping and attribute synchronization.
Enhanced Static Analyzer for Offline Mode
The static analyzer now supports offline mode validation using the --offline flag. This update checks that every namespace with APIs has the required APIAuth resources and confirms that each APIPortal resource is linked to an APIPortalAuth configuration. The analyzer generates tables that show which authentication method is assigned to each API and application, and the diff tool now includes tables that clarify how changes to APIAuth or APIPortalAuth affect your APIs and applications. These improvements help you verify that your offline API management setup is complete and correctly organized before deployment.
For more details, see the API Management Offline Mode, APIAuth, and APIPortalAuth documentation.
New Middleware: Query
We are excited to announce the new Query middleware, which allows you to manipulate query parameters in HTTP requests before forwarding them to services.
This middleware provides a flexible way to modify query parameters in a request, including setting, appending, removing, and renaming them.
For more details, see the Query middleware documentation.
Compatibility Matrix
This release comes with the following components:
| Component | Version |
|---|---|
| Traefik Hub | v3.18.0-beta1 |
| Helm Chart | v37.0.0 |
| Traefik Proxy | v3.4.5 |
| Coraza WAF | v3.3.3 |
| OWASP CRS | v4.14.0 |
| Static Analyzer | v1.5.0 |
| Kubernetes Gateway API | v1.2.1 |
Bug Fixes Timeline
- 2025-06-23: Traefik Hub v3.17.3 and v3.16.6 were released with the following fix:
- Fixed CVE-2025-54386.
June 2025
What's New
AI Gateway General Availability
- AI Gateway graduates from experimental: enable all AI features with
--set hub.aigateway.enabled=true. - New chat-completion middleware replaces the experimental
AIService, adds GenAI metrics, and centralises governance ofmodeland generation parameters. - Model-based routing: use the
Model(`<pattern>`)matcher to steer traffic by JSONmodelfield. - Request-size guard:
hub.aigateway.maxRequestBodySizeprevents OOM/DoS from oversized bodies. - Semantic Cache gains a chat-specific variant, Weaviate vector DB support, and additional vectorizers (Azure OpenAI, Cohere, Gemini, Bedrock).
- Content Guard now offers a chat-aware variant with stream support.
For more details, see the AI Gateway documentation.
Managed Applications (API Management)
Traefik Hub API Management now lets platform teams fully automate application onboarding with the new ManagedApplication resource. Publishers can declaratively create applications, pre-provision API keys, and bind them to ManagedSubscription objects — all without any consumer interaction with the Developer Portal.
Key capabilities include:
- GitOps-friendly
ManagedApplicationresource that storesappId, JWT / API Keys, owner ID, optional notes, and zero-to-many API keys (secrets may be provided inline or by reference). - Publishers provision the
appId, and quotas up front; consumers can call the API straight away - Updated
ManagedSubscriptionresource with amanagedApplicationsselector for explicit targeting of managed apps. - API consumers authenticate immediately with JWT or API keys issued by the publisher; no portal login is required.
- The Hub dashboard lists both managed and self-service applications, with clear indicators and full key management.
- Static-Analyzer rule warns if multiple ManagedApplications share the same
appIdwithin a namespace.
See the Managed Applications documentation for more information.
Offline Mode
Traefik Hub now supports offline mode, which allows you to run the Traefik Hub API Gateway in a completely offline environment.
For more details, see the Offline Mode documentation.
Compatibility Matrix
This release comes with the following components:
| Component | Version |
|---|---|
| Traefik Hub | v3.17.0 |
| Helm Chart | v36.3.0 |
| Traefik Proxy | v3.4.1 |
| Coraza WAF | v3.3.3 |
| OWASP CRS | v4.7.0 |
| Static Analyzer | v1.4.0 |
| Kubernetes Gateway API | v1.2.1 |
Bug Fixes Timeline
- 2025-06-23: Traefik Hub v3.16.2 and v3.15.3 were released with the following fix:
- Fixed CVE-2025-47952.
April 2025
What's New
Multi-Tenant Installation on Kubernetes
Traefik Hub now supports deploying multiple, isolated gateway instances on a single Kubernetes cluster. By configuring specific namespaces for each instance, you can achieve resource isolation, simplify deployments aligned with team structures, and maintain consistent API management across different environments within the same cluster.
Learn more about this feature in the multi-tenancy documentation.
OpenAPI v3.1.x Support
Traefik Hub now supports OpenAPI v3.1.x, in addition to Swagger v2.0 and OpenAPI v3.0.x. Swagger v2 specifications are automatically converted to OpenAPI v3.1 upon processing, ensuring consistency across your API documentation within the Hub.
See the OpenAPI documentation for more details.
March 2025
What's New
New Middleware: Semantic Cache
We introduced a Semantic Cache middleware for the AI Gateway, allowing you to store and retrieve responses based on semantic similarity. If a similar request appears, the middleware returns the cached result immediately instead of calling the AI backend again. This feature helps reduce latency and saves on provider costs.
Learn more about this middleware in it's documentation page.
New Middleware: Content Guard
Content Guard is a middleware that protects sensitive data across both AI and API Gateway environments by blocking or masking content before it reaches any upstream service. It helps ensure that confidential data is safeguarded in all scenarios, whether processing AI-specific traffic or general API requests.
Learn more about this middleware in it's documentation page.