dbcve.org
TraefikApplication

CVE-2025-54386

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-02
Fix available
A fix is available. Upgrade to 2.11.7 / 3.4.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A path traversal vulnerability exists in Traefik's WASM plugin installation mechanism. Attackers can supply malicious ZIP archives containing ../ sequences to overwrite arbitrary files on the system outside the intended plugin directory, potentially achieving RCE or denial of service.

MitigationUpgrade Traefik to versions 2.11.28, 3.4.5, or 3.5.0 and review plugin installation logs for signs of exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TraefikApplication
Affected:< 2.11.7>= 3.0.0, < 3.4.4= 3.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Traefik version
    Run 'traefik version' or check the binary metadata
    Affected if The version is < 2.11.7, or >= 3.0.0 and < 3.4.4, or exactly 3.5.0
  2. Verify WASM plugin usage
    Review Traefik configuration files (static and dynamic) for 'experimental' plugins or 'wasm' plugin definitions in the plugins section
    Affected if WASM plugins are defined in the configuration
  3. Inspect plugin download logs
    Examine Traefik logs for plugin download/install operations, looking for signs of ZIP extraction or plugin installation activity
    Affected if Plugin downloads occurred and logs show successful extraction
  4. Review plugin directory for anomalies
    Check the plugin storage directory (default: ./plugins-storage) for unexpected files or directories created outside the expected plugin folder structure
    Affected if Files exist outside the expected plugin subdirectory structure or unexpected directories are present

A user is affected if they run an affected Traefik version and have WASM plugins enabled, with potential exploitation evidenced by unexpected files in or outside the plugin storage directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.11.7 / 3.4.4 or later
Fixed in 2.11.73.4.4
Vendor patch github.com →
Interim mitigation

Upgrade Traefik to versions 2.11.28, 3.4.5, or 3.5.0 and review plugin installation logs for signs of exploitation.

Recommended fix High confidence

Traefik 2.11.28+ (for 2.x users) or 3.4.5+/3.5.0+ (for 3.x users)

  1. Identify your current Traefik version using `traefik version` or checking your deployment manifests
  2. For Traefik 2.x users: Upgrade to version 2.11.28 or later
  3. For Traefik 3.x users: Upgrade to version 3.4.5 or later (or 3.5.0 stable if using the 3.5.x line)
  4. Verify the upgrade was successful by running `traefik version`
  5. Test that your plugins install and function correctly after upgrade
  6. Ensure the plugin installation mechanism works as expected with the security fix applied
Caveat Minimal risk - this is a patch upgrade containing security fixes; review plugin compatibility if using custom plugins

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Traefik Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54386 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54386 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data