VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

flask-cors: vulnerability history, versions and safety

flask-cors is a package in the PyPI ecosystem. Vulert records 13 vulnerabilities for it across 64 releases, from Aug 2020 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
13 vulnerabilities recorded H2 M4 U7
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
3 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all flask-cors vulnerabilities

Vulert verdict on flask-cors 6.0.5 i

Updated on 23 Oct 2026

Careful: 6.0.5 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 6.0.5 — affected i
  • Vulnerabilities on record 13 over 5 years · 3 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 2 i
  • Depended on by 2,248 packages i
  • Stars 933 i
  • OpenSSF scorecard 4/10 i
  • Last release 4 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for flask-cors, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
6.0.5 08 Jun 2026 U2 MIT No Details →
6.0.4 07 Jun 2026 U2 MIT No Details →
6.0.3 06 Jun 2026 U2 MIT No Details →
6.0.3rc0 06 Jun 2026 U2 MIT No Details →
6.0.2 12 Dec 2025 U1 MIT No Details →
6.0.1 11 Jun 2025 U1 — No Details →
6.0.1.dev0 11 Jun 2025 U1 — No Details →
6.0.0 17 May 2025 U1 — No Details →
5.0.1 24 Feb 2025 M3 U4 — No Details →
0.0.0.dev4 24 Feb 2025 H1 M3 U4 — No Details →
0.0.0.dev3 24 Feb 2025 H1 M3 U4 — No Details →
5.0.0 31 Aug 2024 M3 U4 MIT No Details →
4.0.2 30 Aug 2024 M3 U4 MIT No Details →
4.0.1 04 May 2024 H1 M3 U5 MIT No Details →
4.0.0 26 Jun 2023 H1 M4 U5 MIT No Details →
4.0.0a0 26 Jun 2023 H1 M4 U5 MIT No Details →
3.0.10 06 Jan 2021 H1 M4 U5 MIT No Details →
3.0.9 30 Aug 2020 H1 M4 U5 MIT No Details →
3.0.8 08 Jun 2019 H2 M4 U6 MIT No Details →
3.0.7 09 Nov 2018 H2 M4 U6 MIT No Details →
3.0.6 12 Jun 2018 H2 M4 U6 MIT No Details →
3.0.4 26 Apr 2018 H2 M4 U6 MIT No Details →
3.0.3 28 Jun 2017 H2 M4 U6 MIT No Details →
3.0.2 08 Sep 2016 H2 M4 U6 MIT No Details →
3.0.1 31 Aug 2016 H2 M4 U6 MIT No Details →
3.0.0 20 Aug 2016 H2 M4 U6 MIT No Details →
2.1.3 18 Aug 2016 H2 M4 U6 MIT No Details →
2.1.2 08 Nov 2015 H2 M4 U6 MIT No Details →
2.1.1 08 Nov 2015 H2 M4 U6 MIT No Details →
2.1.0 05 Aug 2015 H2 M4 U6 MIT No Details →
2.0.1 08 May 2015 H2 M4 U6 MIT No Details →
2.0.0 24 Mar 2015 H2 M4 U6 MIT No Details →
2.0.0rc1 15 Mar 2015 H2 M4 U6 MIT No Details →
1.10.3 13 Feb 2015 H2 M4 U6 MIT No Details →
1.10.2 18 Dec 2014 H2 M4 U6 MIT No Details →
1.10.1 13 Dec 2014 H2 M4 U6 MIT No Details →
1.10.0 11 Dec 2014 H2 M4 U6 MIT No Details →
1.9.0 20 Sep 2014 H2 M4 U6 MIT No Details →
1.8.1 18 Sep 2014 H2 M4 U6 MIT No Details →
1.8.0 22 Aug 2014 H2 M4 U6 MIT No Details →
1.7.4 14 Aug 2014 H2 M4 U6 MIT No Details →
1.7.3 12 Aug 2014 H2 M4 U6 MIT No Details →
1.7.2 11 Aug 2014 H2 M4 U6 MIT No Details →
1.7.1 10 Aug 2014 H2 M4 U6 MIT No Details →
1.7.0 09 Aug 2014 H2 M4 U6 MIT No Details →
1.6.1 31 Jul 2014 H2 M4 U6 MIT No Details →
1.6.0 30 Jul 2014 H2 M4 U6 MIT No Details →
1.5.0 24 Jul 2014 H2 M4 U6 MIT No Details →
1.4.0 23 Jul 2014 H2 M4 U6 MIT No Details →
1.3.1 19 May 2014 H2 M4 U6 MIT No Details →
1.3.0 22 Apr 2014 H2 M4 U6 MIT No Details →
1.2.1 28 Mar 2014 H2 M4 U6 MIT No Details →
1.2.0 13 Mar 2014 H2 M4 U6 MIT No Details →
1.1.3 06 Mar 2014 H2 M4 U6 MIT No Details →
1.1.2 26 Feb 2014 H2 M4 U6 MIT No Details →
1.1.1 24 Jan 2014 H2 M4 U6 MIT No Details →
1.1.0 24 Dec 2013 H2 M4 U7 MIT No Details →
1.0.0 28 Jul 2013 H2 M4 U7 MIT No Details →
2.1.1-py2.7 — H2 M4 U7 — No Details →
2.1.2-py2.7 — H2 M4 U7 — No Details →
3.0.0-py2.7 — H2 M4 U7 — No Details →
3.0.1-py2.7 — H2 M4 U7 — No Details →
3.0.2-py2.7 — H2 M4 U7 — No Details →
3.0.3-py2.7 — H2 M4 U7 — No Details →

All 64 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2021 1
  • 2024 5
  • 2025 3
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 13 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for flask-cors

The 5 most severe of 13 vulnerabilities recorded for this package

Search all 13 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-6221: Vulnerability in flask-cors version 4.0.1 7.5 high 4.0.2 18 Aug 2024
CVE-2024-6221: flask-cors Vulnerability Exposes Private Network Resources 7.5 high No fix published 18 Aug 2024
CVE-2020-25032: Insecure input handling in Flask-Cors 7.5 high 3.0.9 06 May 2021
CVE-2024-6221: Flask-CORS allows Access-Control-Allow-Private-Network header to be set to true by default 7.5 high 4.0.2 18 Aug 2024
CVE-2024-1681: flask-cors Log Injection Vulnerability 5.3 medium No fix published 19 Apr 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About flask-cors

Is flask-cors safe to use?

Vulert records 13 vulnerabilities for flask-cors in PyPI: 0 critical, 2 high, 4 medium and 0 low, plus 7 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is flask-cors's Vulert package health score?

Vulert scores flask-cors 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of flask-cors affected?

Yes. 6.0.5, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of flask-cors should I use?

6.0.5 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does flask-cors have?

13 vulnerabilities are recorded for flask-cors in the PyPI ecosystem: 0 critical, 2 high, 4 medium and 0 low, plus 7 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new flask-cors vulnerabilities disclosed?

3 vulnerabilities were recorded for flask-cors in the last 12 months, and the oldest entry in this database dates to 31 Aug 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of flask-cors are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor flask-cors for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the flask-cors version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.