CVE-2026-48817: Starlette · Arbitrary HTTP method dispatched to `HTTPEndpoint` attributes via `getattr`
Affects snyk-agent-scanSource GCVE Database
Not known to be exploited · CVSS 5.3 Medium : upgrade to 0.5.5 when convenient.
Data as of 1 Nov 2026, 01:50 UTC
- Patch
- Available – fixed in 0.5.5
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 31 Oct 2026.
What to do
Upgrade snyk-agent-scan to 0.5.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewsnyk-agent-scanpkg:brew/snyk-agent-scanOther 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
Apply the official fix by upgrading Starlette to version 0.5.5 or later. Alternatively, ensure that all HTTPEndpoint subclasses are registered with an explicit methods= argument 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 invocation of unintended attributes. No other mitigation is required if these steps are followed.
Description
Starlette's HTTPEndpoint dispatches HTTP methods by lowercasing the method name and using getattr without restricting to known HTTP verbs. If an HTTPEndpoint subclass is registered via Route without specifying allowed methods, any HTTP method, including non-standard ones, can invoke attributes on the endpoint. This allows attackers to call internal methods not intended as HTTP handlers, potentially bypassing authorization checks. The issue affects Starlette versions from 0.4.3 up to but not including 0.5.5 and frameworks built on it like FastAPI. A fix is available in version 0.5.5 by explicitly specifying allowed HTTP methods in Route registrations.