Skip to main content
VulnerabilityPublished

CVE-2025-47952: traefik · Path Traversal

Affects traefikSource CVE Database V5

0

Public exploit available · CVSS 2.9 Low : upgrade to 3.4.1 or 2.11.25 as a priority.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score
2.9Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 62% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.4.1, 2.11.25
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 May 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade traefik/traefik to 3.4.1 or 2.11.25.

Affected software

ProductAffectedFixed in
GitHubtraefik/traefikpkg:github/traefik/traefikOther threatsAffected
  • <2.11.25
  • <3.4.1
Fixed in
  • 2.11.25
  • 3.4.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediate upgrade of Traefik to versions 2.11.25 or 3.4.1 or later to apply the official patch addressing this vulnerability.
  2. Review and audit Traefik routing configurations, especially those using PathPrefix, Path, or PathRegex matchers, to ensure no unintended backend exposure exists.
  3. Implement strict input validation and normalization on URL paths at the application or proxy level to detect and block suspicious URL-encoded sequences that could be used for traversal.
  4. Employ network segmentation and zero-trust principles to limit backend service exposure, ensuring that even if routing is bypassed, access to sensitive services is controlled.
  5. Monitor Traefik logs for unusual or malformed URL requests that may indicate attempted exploitation.
  6. Use Web Application Firewalls (WAFs) or API gateways with rules to detect and block path traversal attempts.
  7. Conduct penetration testing focused on proxy routing logic to identify any residual or related vulnerabilities.

Description

Traefik (pronounced traffic) is an HTTP reverse proxy and load balancer. Prior to versions 2.11.25 and 3.4.1, 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 URL encoded string 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.25 and 3.4.1.

References

Community reviews

Loading reviews…