CVE-2026-48817: Starlette · Arbitrary HTTP method dispatched to `HTTPEndpoint` attributes via `getattr`
Affects fastapiSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.136.3 when convenient.
Data as of 9 Nov 2026, 20:03 UTC
- Patch
- Available – fixed in 0.136.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade fastapi to 0.136.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewfastapipkg:brew/fastapiOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Register HTTPEndpoint subclasses with an explicit methods= argument on the Route, listing only the supported HTTP verbs. This causes the route to reject any other HTTP methods with a 405 Method Not Allowed response before reaching the endpoint, preventing non-standard methods from invoking internal attributes. Additionally, upgrade Starlette to version 0.136.3 or later where this issue is fixed.
Description
Starlette's HTTPEndpoint dispatches HTTP methods by lowercasing the method name and using getattr to call an attribute, without restricting to known HTTP verbs. If a route is registered without an explicit methods= argument, non-standard HTTP methods can invoke internal endpoint attributes not intended as handlers. This can lead to unauthorized invocation of internal methods. FastAPI and other frameworks built on Starlette are also affected. The issue is fixed in Starlette version 0.136.3 by requiring explicit method constraints on routes.