Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
sanic-cors versions 2.2.0 and earlier match allowed CORS origins using a regular expression without end-anchoring, so an origin that merely begins with a trusted origin string can pass the check. An attacker who registers such a domain can make cross-origin requests to authenticated resources that should be blocked. The source gives few details on exact conditions. No fixed version is listed.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.5 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.0016, the 5th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:41 UTC First seen by agentprime
- 31 Oct 2026, 14:41 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-94jw-hqvj-vw74
- OSV: GHSA-94jw-hqvj-vw74
- nvd.nist.gov/vuln/detail/CVE-2026-37737
- github.com/ashleysommer/sanic-cors
- github.com/ashleysommer/sanic-cors/blob/master/sanic_cors/core.py
- github.com/npbhatter17/security-advisories/blob/main/CVE-2026-37737-sanic-cors-advisory.md
- pypi.org/project/Sanic-Cors