Skip to main content
VulnerabilityPublished Updated

CVE-2025-32431: github.com/traefik/traefik · Traefik has a possible vulnerability with its path matchers

Affects github.com/traefik/traefikSource GCVE Database

0
Compare

Public exploit available · CVSS 9.3 Critical · fixed in 2.11.23 : patch github.com/traefik/traefik as a priority.

Data as of 19 Nov 2026, 02:13 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 2.11.23, 3.3.6, 3.4.0-rc2
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Apr 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: 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 18 Nov 2026.

What to do

Upgrade github.com/traefik/traefik/v2 to 2.11.23; github.com/traefik/traefik/v3 to 3.3.6; github.com/traefik/traefik/v3 to 3.4.0-rc2.

Affected software

ProductAffectedFixed in
Gogithub.com/traefik/traefikAffected
  • <=1.7.34
Fixed in–
Gogithub.com/traefik/traefik/v2Affected
  • <2.11.23
Fixed in
  • 2.11.23
Gogithub.com/traefik/traefik/v3Affected
  • <3.3.6
Fixed in
  • 3.3.6
Gogithub.com/traefik/traefik/v3Affected
  • >=3.4.0-rc1 <3.4.0-rc2
  • =3.4.0-rc1
Fixed in
  • 3.4.0-rc2

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

Description

## Impact 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. ## Example ```yaml apiVersion: traefik.io/v1alpha1 kind: IngressRoute metadata: name: my-service spec: routes: - match: PathPrefix(‘/service’) kind: Rule services: - name: service-a port: 8080 middlewares: - name: my-middleware-a - match: PathPrefix(‘/service/sub-path’) kind: Rule services: - name: service-a port: 8080 ``` In such a case, the request `http://mydomain.example.com/service/sub-path/../other-path` will reach the backend `my-service-a` without operating the middleware `my-middleware-a` unless the computed path is `http://mydomain.example.com/service/other-path` and should be computes by the first router (operating `my-middleware-a`). ## Patches - https://github.com/traefik/traefik/releases/tag/v2.11.24 - https://github.com/traefik/traefik/releases/tag/v3.3.6 - https://github.com/traefik/traefik/releases/tag/v3.4.0-rc2 ## Workaround Add a `PathRegexp` rule to the matcher to prevent matching a route with a `/../` in the path. Example: ```yaml match: PathPrefix(`/service`) && !PathRegexp(`(?:(/\.\./)+.*)`) ``` ## For more information If you have any questions or comments about this advisory, please [open an issue](https://github.com/traefik/traefik/issues).

References

Community reviews

Loading reviews…