Advisory

GHSA-j65m-hv65-r264

Details, part 2 of 2. The advisory

Details

Suggested Remediation

  1. Apply RateLimitMiddleware in the production handler chain for authenticated routes.
  2. Derive the rate-limit key from the immediate peer IP by default instead of trusting client-supplied forwarded headers.
  3. Do not exempt auth-checkable endpoints such as /health and /metrics from rate limiting.
  4. Consider an additional auth-failure throttle so repeated invalid token attempts are constrained even when endpoint-level behavior changes in the future.

Screenshot capture
<img width="553" height="105" alt="ภาพถ่ายหน้าจอ 2569-03-18 เวลา 13 03 01" src="https://github.com/user-attachments/assets/ab5cd7af-5a67-40ae-aae3-1f4737afd32e" />

Sources & licences