VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

flash-attn: vulnerability history, versions and safety

flash-attn is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 77 releases, from May 2026 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
2 vulnerabilities recorded H1 U1
i
2 with no fix published

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

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

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all flash-attn vulnerabilities

Vulert verdict on flash-attn 2.8.3.post2 i

Updated on 23 Oct 2026

Careful: 2.8.3.post2 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 Active

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 2.8.3.post2 — affected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 7.3 i
  • With no published fix 2 i
  • Depended on by 62 packages i
  • Stars 25,181 i
  • Last release this month 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 flash-attn, 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.8.3.post2 14 Oct 2026 H1 U1 non-standard No Details →
2.8.3.post1 11 Jun 2026 H1 U1 non-standard No Details →
2.8.3 15 Aug 2025 H1 U1 non-standard No Details →
2.8.2 24 Jul 2025 H1 U1 non-standard No Details →
2.8.1 10 Jul 2025 H1 U1 non-standard No Details →
2.8.0.post2 15 Jun 2025 H1 U1 non-standard No Details →
2.7.4.post1 30 Jan 2025 H1 U1 non-standard No Details →
2.7.3 12 Jan 2025 H1 U1 non-standard No Details →
2.7.2.post1 08 Dec 2024 H1 U1 non-standard No Details →
2.7.1.post4 07 Dec 2024 H1 U1 non-standard No Details →
2.7.0.post2 13 Nov 2024 H1 U1 non-standard No Details →
2.6.3 25 Jul 2024 H1 U1 non-standard No Details →
2.6.2 23 Jul 2024 H1 U1 non-standard No Details →
2.6.1 13 Jul 2024 H1 U1 non-standard No Details →
2.6.0.post1 11 Jul 2024 H1 U1 non-standard No Details →
2.5.9.post1 27 May 2024 H1 U1 non-standard No Details →
2.5.8 26 Apr 2024 H1 U1 non-standard No Details →
2.5.7 08 Apr 2024 H1 U1 non-standard No Details →
2.5.6 02 Mar 2024 H1 U1 non-standard No Details →
2.5.5 22 Feb 2024 H1 U1 non-standard No Details →
2.5.4 21 Feb 2024 H1 U1 non-standard No Details →
2.5.3 10 Feb 2024 H1 U1 non-standard No Details →
2.5.2 31 Jan 2024 H1 U1 non-standard No Details →
2.5.1.post1 31 Jan 2024 H1 U1 non-standard No Details →
2.5.0 23 Jan 2024 H1 U1 non-standard No Details →
2.4.3.post1 22 Jan 2024 H1 U1 non-standard No Details →
2.4.2 26 Dec 2023 H1 U1 non-standard No Details →
2.4.1 24 Dec 2023 H1 U1 non-standard No Details →
2.4.0.post1 22 Dec 2023 H1 U1 non-standard No Details →
2.3.6 28 Nov 2023 H1 U1 non-standard No Details →
2.3.5 27 Nov 2023 H1 U1 non-standard No Details →
2.3.4 20 Nov 2023 H1 U1 non-standard No Details →
2.3.3 24 Oct 2023 H1 U1 non-standard No Details →
2.3.2 09 Oct 2023 H1 U1 non-standard No Details →
2.3.1.post1 04 Oct 2023 H1 U1 non-standard No Details →
2.3.0 27 Sep 2023 H1 U1 non-standard No Details →
2.2.5 24 Sep 2023 H1 U1 non-standard No Details →
2.2.4.post1 22 Sep 2023 H1 U1 non-standard No Details →
2.2.4 21 Sep 2023 H1 U1 non-standard No Details →
2.2.3.post2 19 Sep 2023 H1 U1 non-standard No Details →
2.2.2 11 Sep 2023 H1 U1 non-standard No Details →
2.2.1 06 Sep 2023 H1 U1 non-standard No Details →
2.2.0 06 Sep 2023 H1 U1 non-standard No Details →
2.1.2.post3 04 Sep 2023 H1 U1 non-standard No Details →
2.1.1 28 Aug 2023 H1 U1 non-standard No Details →
2.1.0 25 Aug 2023 H1 U1 non-standard No Details →
2.0.9 22 Aug 2023 H1 U1 non-standard No Details →
2.0.8 17 Aug 2023 H1 U1 non-standard No Details →
2.0.7 15 Aug 2023 H1 U1 non-standard No Details →
2.0.6.post2 14 Aug 2023 H1 U1 non-standard No Details →
2.0.6 14 Aug 2023 H1 U1 non-standard No Details →
2.0.5 13 Aug 2023 H1 U1 non-standard No Details →
2.0.4 01 Aug 2023 H1 U1 non-standard No Details →
2.0.3 01 Aug 2023 H1 U1 non-standard No Details →
2.0.2 28 Jul 2023 H1 U1 non-standard No Details →
2.0.1 24 Jul 2023 H1 U1 non-standard No Details →
2.0.0.post1 17 Jul 2023 H1 U1 non-standard No Details →
1.0.9 17 Jul 2023 H1 U1 non-standard No Details →
1.0.8 03 Jul 2023 H1 U1 non-standard No Details →
1.0.7 30 May 2023 H1 U1 non-standard No Details →
1.0.6 27 May 2023 H1 U1 non-standard No Details →
1.0.5 12 May 2023 H1 U1 non-standard No Details →
1.0.4 26 Apr 2023 H1 U1 non-standard No Details →
1.0.3.post0 21 Apr 2023 H1 U1 non-standard No Details →
1.0.3 21 Apr 2023 H1 U1 non-standard No Details →
1.0.2 16 Apr 2023 H1 U1 non-standard No Details →
1.0.1 12 Apr 2023 H1 U1 non-standard No Details →
1.0.0 12 Apr 2023 H1 U1 non-standard No Details →
0.2.8 19 Jan 2023 H1 U1 non-standard No Details →
0.2.7 07 Jan 2023 H1 U1 non-standard No Details →
0.2.6.post1 28 Dec 2022 H1 U1 non-standard No Details →
0.2.5 21 Dec 2022 H1 U1 non-standard No Details →
0.2.4 14 Dec 2022 H1 U1 non-standard No Details →
0.2.3 13 Dec 2022 H1 U1 non-standard No Details →
0.2.2 26 Nov 2022 H1 U1 non-standard No Details →
0.2.1 22 Nov 2022 H1 U1 non-standard No Details →
0.2.0 15 Nov 2022 H1 U1 non-standard No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for flash-attn

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-31253: flash-attn Insecure Deserialization Vulnerability in Checkpoint Loading Mechanism 7.3 high No fix published 11 May 2026
CVE-2026-31253: flash-attn Insecure Deserialization Vulnerability in Checkpoint Loading Mechanism 7.3 high No fix published 13 Jul 2026

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 flash-attn

Is flash-attn safe to use?

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

What is flash-attn's Vulert package health score?

Vulert scores flash-attn 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 flash-attn affected?

Yes. 2.8.3.post2, 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 flash-attn should I use?

2.8.3.post2 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 flash-attn have?

2 vulnerabilities are recorded for flash-attn in the PyPI ecosystem: 0 critical, 1 high, 0 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 flash-attn vulnerabilities disclosed?

2 vulnerabilities were recorded for flash-attn in the last 12 months, and the oldest entry in this database dates to 11 May 2026. 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 flash-attn 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 flash-attn for upcoming vulnerabilities?

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