Advisory record · GHSA-43qf-4rqw-9q2g

Flask-CORS vulnerable to Improper Handling of Case Sensitivity

CVSS 5.3 MediumEPSS 0.0072 · 54th percentile

Published by the GitHub Advisory Database at 20 Mar 2025, 12:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
flask-corsPyPI<6.0.06.0.0
Identifiers
GHSA-43qf-4rqw-9q2g · CVE-2024-6866 · PYSEC-2026-1383
Weakness (CWE)
CWE-178
Published
20 Mar 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Flask-CORS versions before 6.0.0 match request paths case-insensitively, although URL paths are case-sensitive, so CORS rules meant for one path can also apply to differently cased variants. The source describes this as allowing unauthorized origins to reach restricted paths and expose data, but gives few other details, such as which configurations are affected. Upgrade flask-cors to 6.0.0 or later.

Written 4 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

ScoreRatingCVSSVectorSource
5.3 Medium 3.0 CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.0072, the 54th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:29 UTC First seen by agentprime
  2. 31 Oct 2026, 14:29 UTC Confirmed by OSV

Sources

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.