# sanic-cors contains an improper regular expression in the try_match() function

Advisory record · `GHSA-94jw-hqvj-vw74`

- **Identifiers:** `GHSA-94jw-hqvj-vw74` · `CVE-2026-37737` · `PYSEC-2026-3539`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-346](https://cwe.mitre.org/data/definitions/346.html) · [CWE-625](https://cwe.mitre.org/data/definitions/625.html)
- **Tags:** [CWE-346](https://agentprime.io/advisories/tag/cwe-346.md) · [CWE-625](https://agentprime.io/advisories/tag/cwe-625.md)
- **Published:** 5 Jun 2026
- **Updated:** 23 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 5 Jun 2026, 15:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `sanic-cors` (PyPI): affected `<=2.2.0`; no fixed version yet

## 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.

Written 5 Nov 2026.

## 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

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`, from 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](https://osv.dev/vulnerability/GHSA-94jw-hqvj-vw74)

## Sources

- [GitHub Advisory Database: GHSA-94jw-hqvj-vw74](https://github.com/advisories/GHSA-94jw-hqvj-vw74)
- [OSV: GHSA-94jw-hqvj-vw74](https://osv.dev/vulnerability/GHSA-94jw-hqvj-vw74)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-37737>
- <https://github.com/ashleysommer/sanic-cors>
- <https://github.com/ashleysommer/sanic-cors/blob/master/sanic_cors/core.py>
- <https://github.com/npbhatter17/security-advisories/blob/main/CVE-2026-37737-sanic-cors-advisory.md>
- <https://pypi.org/project/Sanic-Cors>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-94jw-hqvj-vw74>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-94jw-hqvj-vw74/>. Everything for agents: <https://agentprime.io/llms.txt>.