VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

flask-admin: vulnerability history, versions and safety

flask-admin is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 33 releases, from Sep 2018 to Dec 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all flask-admin vulnerabilities

Vulert verdict on flask-admin 2.2.1 i

Updated on 23 Oct 2026

Good news: 2.2.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 92/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

What to do: Stay on 2.2.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.2.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.2.1 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 19 Dec 2018 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Depended on by 89 packages i
  • Stars 6,070 i
  • Last release 1 month ago i
  • Licence non-standard 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-admin, 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
2.2.1 21 Sep 2026 none non-standard — Details →
2.2.0 07 May 2026 none non-standard — Details →
2.1.0 28 Apr 2026 none non-standard — Details →
2.0.2 11 Nov 2025 none non-standard — Details →
2.0.1 02 Nov 2025 none non-standard — Details →
2.0.0 25 Oct 2025 none non-standard — Details →
2.0.0rc2 20 Oct 2025 none non-standard — Details →
2.0.0rc1 17 Oct 2025 none non-standard — Details →
2.0.0a5 09 Oct 2025 none non-standard — Details →
2.0.0a4 22 Feb 2025 none non-standard — Details →
2.0.0a3 23 Nov 2024 none non-standard — Details →
2.0.0a2 28 Oct 2024 none non-standard — Details →
2.0.0a1 26 Oct 2024 none non-standard — Details →
2.0.0a0 03 Sep 2024 none non-standard — Details →
1.6.1 20 Feb 2023 none non-standard — Details →
1.6.0 30 Jan 2022 none non-standard — Details →
1.5.8 17 Apr 2021 none non-standard — Details →
1.5.7 26 Oct 2020 none non-standard — Details →
1.5.6 09 Apr 2020 none non-standard — Details →
1.5.5 07 Feb 2020 none non-standard — Details →
1.5.4 16 Oct 2019 none non-standard — Details →
1.5.3 20 Dec 2018 none non-standard — Details →
1.5.2 27 Aug 2018 M1 U1 non-standard Yes Details →
1.5.1 06 Mar 2018 M1 U1 non-standard Yes Details →
1.5.0 12 Mar 2017 M1 U1 non-standard Yes Details →
1.4.2 14 Jun 2016 M1 U1 non-standard Yes Details →
1.4.1 13 Jun 2016 M1 U1 non-standard Yes Details →
1.4.0 02 Jan 2016 M1 U1 non-standard Yes Details →
1.3.0 23 Aug 2015 M1 U1 non-standard Yes Details →
1.2.0 13 Jun 2015 M1 U1 non-standard Yes Details →
1.1.0 02 Mar 2015 M1 U1 non-standard Yes Details →
1.0.9 09 Dec 2014 M1 U1 non-standard Yes Details →
1.0.8 21 Apr 2014 M1 U1 non-standard Yes Details →
1.0.7 19 Jan 2014 M1 U1 non-standard Yes Details →
1.0.6 20 May 2013 M1 U1 non-standard Yes Details →
1.0.5 22 Mar 2013 M1 U1 non-standard Yes Details →
1.0.4 27 Dec 2012 M1 U1 non-standard Yes Details →
1.0.3 05 Nov 2012 M1 U1 non-standard Yes Details →
1.0.2 27 Aug 2012 M1 U1 non-standard Yes Details →
1.0.1 03 May 2012 M1 U1 non-standard Yes Details →
1.0.0 02 May 2012 M1 U1 non-standard Yes Details →
0.4.2 13 Apr 2012 M1 U1 non-standard Yes Details →
0.4.1 13 Apr 2012 M1 U1 non-standard Yes Details →
0.4.0 25 Mar 2012 M1 U1 non-standard Yes Details →
0.3.0 21 Dec 2011 M1 U1 non-standard Yes Details →
0.2.2 20 Oct 2011 M1 U1 non-standard Yes Details →
0.2.1 15 Oct 2011 M1 U1 non-standard Yes Details →
0.2.0 15 Oct 2011 M1 U1 non-standard Yes Details →
0.1.4 16 Sep 2011 M1 U1 non-standard Yes Details →
0.1.3 16 Sep 2011 M1 U1 non-standard Yes Details →
0.1.2 11 Jul 2011 M1 U1 non-standard Yes Details →
0.1.1 11 Jul 2011 M1 U1 non-standard Yes Details →
0.1.0 11 Jul 2011 M1 U1 non-standard Yes Details →
0.1.3-py2.7 — M1 U1 — Yes Details →
0.1.3.linux-x86_64 — M1 U1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 2

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

03 Vulnerabilities

Recorded vulnerabilities for flask-admin

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-16516: Cross-Site Scripting in Flask-Admin 6.1 medium 1.5.3 19 Dec 2018
CVE-2018-16516: Reflected XSS in Flask-Admin N/A unrated 1.5.3 05 Sep 2018

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-admin

Is flask-admin safe to use?

Vulert records 2 vulnerabilities for flask-admin in PyPI: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

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

Vulert scores flask-admin 92/100, which reads as healthy. 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).

Is the latest version of flask-admin affected?

No. 2.2.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of flask-admin should I use?

2.2.1 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-admin have?

2 vulnerabilities are recorded for flask-admin in the PyPI ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 1 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-admin vulnerabilities disclosed?

0 vulnerabilities were recorded for flask-admin in the last 12 months, and the oldest entry in this database dates to 05 Sep 2018. 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-admin 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-admin for upcoming vulnerabilities?

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