# CVE-2025-32431: Traefik has a possible vulnerability with the path matchers > Attackers can bypass middleware chains and access restricted backends by using path traversal sequences in URLs when specific path matchers are configured. - **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:P`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 21 Apr 2025 - **Updated:** 21 Apr 2025 - **Also known as:** ECHO-5622-1894-e085, GHSA-6p68-w45g-48j7, GO-2025-3634, MINI-5fcw-ph6w-2fcc, MINI-f5rm-4chp-xcgq ## What is CVE-2025-32431? CVE-2025-32431 is a high-severity path traversal vulnerability in Traefik Traefik, published on 21 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Traefik (pronounced traffic) is an HTTP reverse proxy and load balancer. In versions prior to 2.11.24, 3.3.6, and 3.4.0-rc2. There is a potential vulnerability in Traefik managing the requests using a PathPrefix, Path or PathRegex matcher. When Traefik is configured to route the requests to a backend using a matcher based on the path, if the URL contains a /../ in its path, it’s possible to target a backend, exposed using another router, by-passing the middlewares chain. This issue has been patched in versions 2.11.24, 3.3.6, and 3.4.0-rc2. A workaround involves adding a `PathRegexp` rule to the matcher to prevent matching a route with a `/../` in the path. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2025-32431? 11 open source packages ship an affected version, including github.com/traefik/traefik/v3, github.com/traefik/traefik and github.com/traefik/traefik/v2. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/traefik/traefik/v3` | Go | All versions | 3.3.6, 3.4.0-rc2 | | `github.com/traefik/traefik/v3` | Go | All versions | 3.3.6 | | `github.com/traefik/traefik/v3` | Go | All versions | 3.3.6 | | `github.com/traefik/traefik/v3` | Go | From 3.4.0-rc1 | 3.4.0-rc2 | | `github.com/traefik/traefik/v3` | Go | From 3.4.0-rc1 | 3.4.0-rc2 | | `github.com/traefik/traefik` | Go | All versions | None | | `github.com/traefik/traefik` | Go | All versions to 1.7.34 | None | | `github.com/traefik/traefik` | Go | All versions to 1.7.34 | None | | `github.com/traefik/traefik/v2` | Go | All versions | 2.11.23 | | `github.com/traefik/traefik/v2` | Go | All versions | 2.11.23 | | `github.com/traefik/traefik/v2` | Go | All versions | 2.11.23 | Products: Traefik Traefik. ## How do I fix CVE-2025-32431? Upgrade github.com/traefik/traefik/v3 to a fixed version for your release line: 3.3.6 or 3.4.0-rc2. ## Is CVE-2025-32431 being exploited? There is no known exploitation of CVE-2025-32431 in the wild and no public exploit code. ## Other vulnerabilities in Traefik Traefik - [CVE-2024-45410](https://insights.sbomify.com/CVE-2024-45410/): HTTP client can remove the X-Forwarded headers in Traefik (critical 9.8) - [CVE-2026-88877](https://insights.sbomify.com/CVE-2026-88877/): Traefik v3.7.0 Authentication Bypass via from-to-www-redirect (critical 9.3) - [CVE-2026-85595](https://insights.sbomify.com/CVE-2026-85595/): Traefik before v2.11.55 and v3.0.0 through v3.7.10 Authentication Bypass via digestAuth (critical 9.3) - [CVE-2026-88007](https://insights.sbomify.com/CVE-2026-88007/): Traefik HTTP/3 Backend NTLM Connection Reuse (critical 9.1) - [CVE-2026-88009](https://insights.sbomify.com/CVE-2026-88009/): Traefik: Rootless HTTP/1 request-target routes as "/" but is forwarded verbatim, bypassing path-scoped routing, middleware guards and access logging (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-32431 and fix it if it is affected. What it is: CVE-2025-32431 is a high-severity path traversal vulnerability in Traefik Traefik, published on 21 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-32431 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.3.6, 3.4.0-rc2 - github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.3.6 - github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.3.6 - github.com/traefik/traefik/v3 (Go): affected from 3.4.0-rc1; fixed in 3.4.0-rc2 - github.com/traefik/traefik/v3 (Go): affected from 3.4.0-rc1; fixed in 3.4.0-rc2 - github.com/traefik/traefik (Go): affected all versions; no fix listed - github.com/traefik/traefik (Go): affected all versions up to 1.7.34; no fix listed - github.com/traefik/traefik (Go): affected all versions up to 1.7.34; no fix listed - github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.23 - github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.23 - github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.23 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-32431/ (Markdown: https://insights.sbomify.com/CVE-2025-32431/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-32431 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-32431 - OSV: https://osv.dev/vulnerability/CVE-2025-32431 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-32431/ Summaries are generated and may contain mistakes; the official description above is the record.