CVE-2025-32431: Traefik Path Traversal Vulnerability

CVE-2025-32431 Overview

CVE-2025-32431 is a path traversal vulnerability affecting Traefik, a popular HTTP reverse proxy and load balancer widely deployed in containerized and microservice environments. The vulnerability exists in how Traefik handles URL path routing when using PathPrefix, Path, or PathRegex matchers. By injecting /../ sequences into request URLs, attackers can bypass the intended router configuration and target backends exposed through different routers, effectively circumventing the entire middleware security chain.

Critical Impact
Attackers can bypass authentication, authorization, rate limiting, and other security middleware by exploiting path traversal in Traefik routing, potentially gaining unauthorized access to protected backend services.

Affected Products

Traefik versions prior to 2.11.24
Traefik versions prior to 3.3.6
Traefik 3.4.0 and 3.4.0-rc1

Discovery Timeline

2025-04-21 - CVE-2025-32431 published to NVD
2025-11-25 - Last updated in NVD database

Technical Details for CVE-2025-32431

Vulnerability Analysis

This vulnerability falls under CWE-22 (Path Traversal) and affects the core routing mechanism of Traefik. When Traefik is configured to route requests to backends using path-based matchers (PathPrefix, Path, or PathRegex), the router does not properly sanitize URL paths containing directory traversal sequences before matching.

The flaw allows attackers to craft malicious URLs containing /../ sequences that manipulate path resolution during the routing phase. This means a request intended for one router can be redirected to match a different router's rules, completely bypassing any middleware (such as authentication, authorization, or rate limiting) that would normally be applied.

The network-accessible nature of this vulnerability combined with no authentication requirements makes it particularly dangerous in environments where Traefik exposes multiple services with different security postures. An attacker with no prior access can potentially reach protected internal services that were assumed to be secured by middleware chains.

Root Cause

The root cause lies in insufficient path normalization during Traefik's request routing process. When a request URL contains relative path components like /../, Traefik's path matchers evaluate the raw path rather than a canonicalized version. This allows path-based routing decisions to be manipulated by attackers, causing requests to be routed through unintended paths while appearing to match legitimate route configurations.

Attack Vector

The attack is network-based and requires no authentication or user interaction. An attacker can exploit this vulnerability by:

Identifying Traefik-fronted services with path-based routing
Crafting HTTP requests with /../ sequences in the URL path
Sending requests that appear to match one route but are processed by another
Bypassing middleware protections (auth, rate limiting, access controls) applied to the legitimate route
Accessing backend services directly without security controls

For example, if /admin is protected by authentication middleware and /public is not, an attacker might craft a request like /public/../admin/sensitive-endpoint to bypass the authentication middleware while still reaching the admin backend.

See the GitHub Security Advisory for additional technical details on exploitation scenarios.

Detection Methods for CVE-2025-32431

Indicators of Compromise

HTTP access logs containing URLs with /../ or %2e%2e%2f sequences in path components
Requests reaching backend services that should be blocked by middleware (authentication failures not occurring when expected)
Unusual traffic patterns to protected endpoints from unauthorized sources
Access log entries showing successful requests to sensitive endpoints without corresponding authentication events

Detection Strategies

Implement log analysis rules to detect path traversal patterns (/../, ..%2f, %2e%2e/) in incoming HTTP request URLs
Deploy Web Application Firewall (WAF) rules to block requests containing directory traversal sequences
Enable Traefik access logging and monitor for requests reaching protected backends without proper authentication headers
Create alerts for requests that match public route patterns but access admin or sensitive backend paths

Monitoring Recommendations

Enable verbose access logging in Traefik to capture full request URLs including path components
Implement real-time monitoring for path traversal attack patterns in proxy logs
Set up correlation rules to detect authentication bypass attempts by comparing middleware events with backend access logs
Monitor for increased error rates or unusual response codes from protected backend services

How to Mitigate CVE-2025-32431

Immediate Actions Required

Upgrade Traefik to patched versions: 2.11.24, 3.3.6, or 3.4.0-rc2 immediately
If immediate upgrade is not possible, implement the PathRegexp workaround to block path traversal in routes
Review Traefik access logs for evidence of exploitation attempts
Audit current Traefik configurations for routes using PathPrefix, Path, or PathRegex matchers

Patch Information

Traefik has released patched versions that address this vulnerability:

Version 2.11.24 - GitHub Release v2.11.24
Version 3.3.6 - GitHub Release v3.3.6
Version 3.4.0-rc2 - GitHub Release v3.4.0-rc2

The fix is detailed in the Traefik Pull Request #11684.

Workarounds

Add a PathRegexp rule to all affected matchers to explicitly reject requests containing /../ in the path
Deploy an upstream WAF or reverse proxy that normalizes paths before forwarding to Traefik
Implement network segmentation to limit access to the Traefik ingress layer
Consider temporarily disabling path-based routing for sensitive services until patching is complete

yaml

# Traefik configuration workaround example
# Add this PathRegexp rule to prevent matching routes with /../ in the path
http:
  routers:
    secure-router:
      rule: "PathPrefix(`/api`) && !PathRegexp(`.*\\.\\./.*`)"
      middlewares:
        - auth-middleware
      service: api-service