Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-37737: n/a

0
Medium
VulnerabilityCVE-2026-37737cvecve-2026-37737
Published: Fri Jun 05 2026 (06/05/2026, 00:00:00 UTC)
Source: CVE Database V5

Description

sanic-cors version 2.2.0 and prior contains an improper regular expression in the try_match() function in sanic_cors/core.py that uses re.match without end-anchoring. This allows an attacker to bypass CORS origin allowlists by registering a domain that begins with a trusted origin string, to gain unauthorized access to cross-origin requests for authenticated resources.

CVSS v3.1

Score 6.5medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 06/05/2026, 15:04:23 UTC

Technical Analysis

The vulnerability in sanic-cors (<= 2.2.0) stems from the use of an unanchored regular expression in the try_match() function within sanic_cors/core.py. This flaw allows an attacker to bypass CORS origin allowlists by registering a domain that begins with a trusted origin string, thereby potentially gaining unauthorized access to cross-origin requests for authenticated resources. The lack of end-anchoring in the regex match leads to this bypass. No CVSS score or vendor advisory is currently available, and no patch or remediation level has been confirmed.

Potential Impact

An attacker can bypass CORS origin allowlists by exploiting the improper regular expression, potentially gaining unauthorized access to cross-origin requests that should be restricted. This could lead to unauthorized access to authenticated resources via cross-origin requests. However, there are no known exploits in the wild at this time.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider additional manual validation of CORS origins or implement alternative controls to restrict cross-origin access. Monitor vendor channels for updates regarding patches or official mitigations.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2026-04-06T00:00:00.000Z
Cvss Version
null
State
PUBLISHED
Remediation Level
null

Threat ID: 6a22e1c9e29bf47b508136b8

Added to database: 6/5/2026, 2:48:41 PM

Last enriched: 6/5/2026, 3:04:23 PM

Last updated: 6/6/2026, 4:58:24 AM

Views: 13

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses