Skip to content
Fencer Vulns
medium 5.3

CVE-2024-6866 json

Case-Insensitive Path Matching in corydolphin/flask-cors

published 2025-03-20 19 mo ago modified 2026-09-10 1 mo ago also GHSA-43qf-4rqw-9q2g , PYSEC-2026-1383 , EUVD-2025-6979

cvss
5.3
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits
0
none known

Summary

corydolphin/flask-cors version 4.01 contains a vulnerability where the request path matching is case-insensitive due to the use of the `try_match` function, which is originally intended for matching hosts. This results in a mismatch because paths in URLs are case-sensitive, but the regex matching treats them as case-insensitive. This misconfiguration can lead to significant security vulnerabilities, allowing unauthorized origins to access paths meant to be restricted, resulting in data exposure and potential data leaks.

Patch / fix

  • pypi flask-cors 6.0.0
  • python-flask-cors Debian 12 3.0.10-2+deb12u1
  • python-flask-cors Debian 14, Debian 13 6.0.0-1

debian advisories DEBIAN-CVE-2024-6866

  • python-flask-cors Ubuntu 22.04 LTS 3.0.9-2ubuntu0.1
  • python-flask-cors Ubuntu Pro 20.04 LTS 3.0.8-2ubuntu0.1+esm1
  • python-flask-cors Ubuntu Pro 24.04 LTS 4.0.0-1ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2024-6866

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • python-Flask-Cors openSUSE Tumbleweed 6.0.2-1.1

opensuse advisories openSUSE-SU-2026:10485-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-6866 updated cvss 5.3

flask-cors: Case-Insensitive Path Matching in corydolphin/flask-cors

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
19 mo ago

Exploit prediction

0.72% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • huntr.com https://huntr.com/bounties/808c11af-faee-43a8-824b-b5ab4f62b9e6 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 5.3 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
OSV 3.0 5.3 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
GitHub 3.0 5.3 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
pypi flask-cors
<6.0.0
6.0.0

Affected products

  • corydolphin corydolphin/flask-cors

Classification

Weakness
  • CWE-178 Improper Handling of Case Sensitivity

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.