Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Flask-CORS versions before 4.0.2 send the Access-Control-Allow-Private-Network header set to true by default, with no configuration option to turn it off. The source gives few details on the exact conditions for exploitation. Upgrade flask-cors to version 4.0.2 or later.
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.0 | CVSS:3.0/AV:N/AC:L/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 21 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:35 UTC First seen by agentprime
- 31 Oct 2026, 14:35 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-hxwh-jpp2-84pm
- OSV: GHSA-hxwh-jpp2-84pm
- nvd.nist.gov/vuln/detail/CVE-2024-6221
- github.com/corydolphin/flask-cors/issues/362
- github.com/corydolphin/flask-cors/pull/363
- github.com/corydolphin/flask-cors/pull/368
- github.com/corydolphin/flask-cors/commit/03aa3f8e2256437f7bad96422a747b98ab5e31bf
- github.com/corydolphin/flask-cors/commit/7ae310c56ac30e0b94fb42129aa377bf633256ec
- github.com/corydolphin/flask-cors/commit/c8514760cf03fcce16d77f6db7007aad429c4548
- github.com/corydolphin/flask-cors
- github.com/corydolphin/flask-cors/releases
- github.com/pypa/advisory-database/tree/main/vulns/flask-cors/PYSEC-2024-260.yaml
- github.com/pypa/advisory-database/tree/main/vulns/flask-cors/PYSEC-2024-71.yaml
- huntr.com/bounties/a42935fc-6f57-4818-bca4-3d528235df4d