Starlette is a lightweight ASGI framework/toolkit. In versions 1.0.1 and below, when dispatching a request, HTTPEndpoint selects the handler by lowercasing the HTTP method and looking it up as an attribute with getattr, without restricting the lookup to a known set of HTTP verbs. When an HTTPEndpoint subclass is registered through Route(...) without an explicit methods= argument, the route does not constrain the method and every method reaches the endpoint. If a non-standard HTTP method whose lowercased name matches an attribute on the endpoint subclass reaches the endpoint, that attribute is invoked as if it were a request handler. An attacker can use this to reach methods that were never meant to be HTTP handlers, such as internal helpers, without the authorization checks applied by the intended public handler. An application (including Starlette-based frameworks like FastAPI) is affected if it registers an HTTPEndpoint subclass via Route(...) without explicitly setting methods=, and that subclass includes extra methods named like non-standard HTTP verbs that take one request argument and return a response. This issue has been fixed in version 1.1.0.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/Kludex/starlette/security/advisories/GHSA-x746-7m8f-x49c Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.3 · encodeNVD modified 2026-10-25 23:10
Affected (CPE criteria) 1
cpe:2.3:a:encode:starlette:*:*:*:*:*:python:*:*
References 2
- https://github.com/Kludex/starlette/releases/tag/1.1.0 Release Notes
- https://github.com/Kludex/starlette/security/advisories/GHSA-x746-7m8f-x49c Mitigation, Vendor Advisory