# CVE-2025-54386: Traefik's Client Plugin is Vulnerable to Path Traversal, Arbitrary File Overwrites and Remote Code Execution > Attackers can exploit path traversal in Traefik's WASM plugin installation to overwrite arbitrary files, leading to remote code execution and privilege escalation. - **Severity:** High 7.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 1 Aug 2025 - **Updated:** 4 Aug 2025 - **Also known as:** CLEANSTART-2026-OD16960, ECHO-6f33-0c94-3aaa, GHSA-q6gg-9f92-r9wg, GO-2025-3835, MINI-jrm5-g9h6-7r2r, MINI-rh9v-34g4-p7pc ## What is CVE-2025-54386? CVE-2025-54386 is a high-severity path traversal vulnerability in Traefik Traefik, published on 1 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. ### Official description Traefik is an HTTP reverse proxy and load balancer. In versions 2.11.27 and below, 3.0.0 through 3.4.4 and 3.5.0-rc1, a path traversal vulnerability was discovered in WASM Traefik’s plugin installation mechanism. By supplying a maliciously crafted ZIP archive containing file paths with ../ sequences, an attacker can overwrite arbitrary files on the system outside of the intended plugin directory. This can lead to remote code execution (RCE), privilege escalation, persistence, or denial of service. This is fixed in versions 2.11.28, 3.4.5 and 3.5.0. Weakness: CWE-30 (Path Traversal: '\dir\..\filename'), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2025-54386? 9 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.4.5, 3.5.0 | | `github.com/traefik/traefik/v3` | Go | All versions | 3.4.5 | | `github.com/traefik/traefik/v3` | Go | All versions | 3.4.5 | | `github.com/traefik/traefik/v3` | Go | From 3.5.0-rc1 | 3.5.0 | | `github.com/traefik/traefik/v3` | Go | From 3.5.0-rc1 | 3.5.0 | | `github.com/traefik/traefik` | Go | All versions | None | | `github.com/traefik/traefik/v2` | Go | All versions | 2.11.28 | | `github.com/traefik/traefik/v2` | Go | All versions | 2.11.28 | | `github.com/traefik/traefik/v2` | Go | All versions | 2.11.28 | Products: Traefik Traefik. ## How do I fix CVE-2025-54386? Upgrade github.com/traefik/traefik/v3 to a fixed version for your release line: 3.4.5 or 3.5.0. ## Is CVE-2025-54386 being exploited? There is no known exploitation of CVE-2025-54386 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-54386 and fix it if it is affected. What it is: CVE-2025-54386 is a high-severity path traversal vulnerability in Traefik Traefik, published on 1 Aug 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2025-54386 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.4.5, 3.5.0 - github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.4.5 - github.com/traefik/traefik/v3 (Go): affected all versions; fixed in 3.4.5 - github.com/traefik/traefik/v3 (Go): affected from 3.5.0-rc1; fixed in 3.5.0 - github.com/traefik/traefik/v3 (Go): affected from 3.5.0-rc1; fixed in 3.5.0 - github.com/traefik/traefik (Go): affected all versions; no fix listed - github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.28 - github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.28 - github.com/traefik/traefik/v2 (Go): affected all versions; fixed in 2.11.28 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-54386/ (Markdown: https://insights.sbomify.com/CVE-2025-54386/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54386 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54386 - OSV: https://osv.dev/vulnerability/CVE-2025-54386 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-54386/ Summaries are generated and may contain mistakes; the official description above is the record.