Most recent entries from all

bdu:2026-00344

2026-10-03T21:41:18.317413+00:00

bdu:2026-00344

certfr-2025-avi-0341 — De multiples vulnérabilités ont été découvertes dans Traefik. Elles permettent à un attaquant de provoquer un contourne…

2026-10-03T21:41:18.317454+00:00

certfr-2025-avi-0341

EUVD-2026-232186

2026-10-03T21:41:18.317474+00:00

EUVD-2026-232186

fkie_cve-2025-32431

2026-10-03T21:41:18.317486+00:00

Traefik (pronounced traffic) is an HTTP reverse proxy and load balancer. In versions prior to 2.11.24, 3.3.6, and 3.4.0-rc2. 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. This issue has been patched in versions 2.11.24, 3.3.6, and 3.4.0-rc2. A workaround involves adding a `PathRegexp` rule to the matcher to prevent matching a route with a `/../` in the path.

GHSA-6p68-w45g-48j7 — Traefik has a possible vulnerability with its path matchers

2026-10-03T21:41:18.317523+00:00

Affected: Go: github.com/traefik/traefik, Go: github.com/traefik/traefik/v2, Go: github.com/traefik/traefik/v3

## 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(`(?:(/\.\./)+.*)`) `…

openSUSE-SU-2025:15017-1 — govulncheck-vulndb-0.0.20250422T181640-1.1 on GA media

2026-10-03T21:41:18.317579+00:00

govulncheck-vulndb-0.0.20250422T181640-1.1 on GA media