The vulnerability exists in Traefik's StripPrefix and StripPrefixRegex middlewares and allows for an authentication bypass. The root cause is a path desynchronization issue. The middlewares would match a prefix on the URL's decoded path but then use the length of that match to slice the raw, percent-encoded path. An attacker could exploit this by including percent-encoded characters, such as %2e (a dot), in the prefix portion of the URL. When the middleware stripped the prefix, it would create a malformed path like /./admin/secret. Authentication middlewares like ForwardAuth would inspect this path, not match it against protected patterns (e.g., /admin/*), and allow the request. However, the backend service would then normalize the path according to RFC 3986, resolving /./admin/secret to /admin/secret and serving the protected content, thus bypassing the authentication control. The patch for this vulnerability involves sanitizing the URL by calling req.URL.JoinPath() after the prefix has been stripped. This function rebuilds the URL, correctly resolving any dot-segments or other path traversal sequences, ensuring that the path sent to subsequent middlewares and the backend is clean and canonical.