Static file handlers can normalize dot segments after route matching, allowing an unauthenticated attacker to read files intended to be protected by route-level middleware. This occurs when protected files are also reachable through a static filesystem mount after path normalization. The issue stems from an incomplete fix where encoded traversal segments, such as `%2E%2E`, bypass guards that only check for encoded path separators like `%2F` and `%5C`. In these cases, the request is unescaped and resolved via `path.Clean`, serving the protected file through a public static route. Additionally, when the `UseEscapedPathForMatching` variable is set to `true`, the router normalizes encoded separators before the static handler checks the wildcard, bypassing the encoded-separator guard.