Skip to content

← Actionable
High, CVSS 8.8

Traefik has a possible vulnerability with its path matchers

CVE-2025-32431GHSA-6p68-w45g-48j7

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Go github.com/traefik/traefik/v3

    Affected
    < 3.3.6>= 3.4.0-rc1, <= 3.4.0-rc1
    Fixed in
    3.3.6, 3.4.0-rc2
  • Go github.com/traefik/traefik/v2

    Affected
    < 2.11.23
    Fixed in
    2.11.23
  • Go github.com/traefik/traefik

    Affected
    <= 1.7.34
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
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 · score source
EPSS
  • CVE-2025-32431: 0.95% estimated exploitation activity in the next 30 days; percentile 61.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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 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: For more…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-6p68-w45g-48j7

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-32431

Advisory: Traefik has a possible vulnerability with its path matchers
IDs: CVE-2025-32431, GHSA-6p68-w45g-48j7
Record: https://patchnext.com/advisories/cve-2025-32431 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/traefik/traefik/v3 3.4.0-rc2, 3.3.6; github.com/traefik/traefik/v2 2.11.23. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/traefik/traefik/v3: affected < 3.3.6; >= 3.4.0-rc1, <= 3.4.0-rc1; fixed in 3.3.6, 3.4.0-rc2
- Go github.com/traefik/traefik/v2: affected < 2.11.23; fixed in 2.11.23
- Go github.com/traefik/traefik: affected <= 1.7.34

## Suggested inspection (read-only)
- Go github.com/traefik/traefik/v3: check the installed version with your package manager.
- Go github.com/traefik/traefik/v2: check the installed version with your package manager.
- Go github.com/traefik/traefik: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/traefik/traefik/v3, github.com/traefik/traefik/v2, github.com/traefik/traefik.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6p68-w45g-48j7 (GitHub-reviewed advisory GHSA-6p68-w45g-48j7 lists affected ranges: Go github.com/traefik/traefik >=0 =0 =0 =3.4.0-rc1 <=3.4.0-rc1)

Commands are suggestions: review each one before running it.

Loading voting…