Vulnerability Database · Hex · Package report

bandit: vulnerability history, versions and safety

bandit is a package in the Hex ecosystem. Vulert records 19 vulnerabilities for it across 120 releases, from May 2026 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
19 vulnerabilities recorded H4 M3 U12
i
1 with no fix published

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

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

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on bandit 1.13.1 i

Updated on 23 Oct 2026

Careful: 1.13.1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

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 1.13.1 — affected i
  • Vulnerabilities on record 19 over 1 year · 19 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 8.7 i
  • With no published fix 1 i
  • Depended on by 16,583,255 packages i
  • Last release this month i

Version list, release dates, licence and dependants published by hex.pm, 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 bandit, 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
1.13.1 15 Oct 2026 U1 — No Details →
1.13.0 15 Oct 2026 U1 — No Details →
1.12.5 20 Aug 2026 U2 — No Details →
1.12.4 27 Jul 2026 U4 — No Details →
1.12.3 25 Jul 2026 U4 — No Details →
1.12.2 25 Jul 2026 U4 — No Details →
1.12.1 24 Jul 2026 U4 — No Details →
1.12.0 06 Jun 2026 U5 — No Details →
1.11.1 13 May 2026 U5 — No Details →
1.11.0 01 May 2026 H2 U7 — No Details →
1.10.4 26 Mar 2026 H4 M3 U11 — No Details →
1.10.3 22 Feb 2026 H4 M3 U11 — No Details →
1.10.2 22 Jan 2026 H4 M3 U11 — No Details →
1.10.1 06 Jan 2026 H4 M3 U11 — No Details →
1.10.0 29 Dec 2025 H4 M3 U11 — No Details →
1.9.0 12 Dec 2025 H4 M3 U11 — No Details →
1.8.0 18 Aug 2025 H4 M3 U11 — No Details →
1.7.0 29 May 2025 H4 M3 U11 — No Details →
1.6.11 31 Mar 2025 H4 M3 U11 — No Details →
1.6.10 26 Mar 2025 H4 M3 U11 — No Details →
1.6.9 21 Mar 2025 H4 M3 U11 — No Details →
1.6.8 05 Mar 2025 H4 M3 U11 — No Details →
1.6.7 30 Jan 2025 H4 M3 U11 — No Details →
1.6.6 25 Jan 2025 H4 M3 U11 — No Details →
1.6.5 15 Jan 2025 H4 M3 U11 — No Details →
1.6.4 11 Jan 2025 H4 M3 U11 — No Details →
1.6.3 08 Jan 2025 H4 M3 U11 — No Details →
1.6.2 04 Jan 2025 H4 M3 U11 — No Details →
1.6.1 06 Dec 2024 H4 M3 U11 — No Details →
1.6.0 18 Nov 2024 H4 M3 U10 — No Details →
1.5.7 01 Aug 2024 H3 M3 U10 — No Details →
1.5.6 01 Aug 2024 H3 M3 U10 — No Details →
1.5.5 19 Jun 2024 H3 M3 U10 — No Details →
1.5.4 14 Jun 2024 H3 M3 U10 — No Details →
1.5.3 07 Jun 2024 H3 M3 U10 — No Details →
1.5.2 10 May 2024 H3 M3 U10 — No Details →
1.5.1 10 May 2024 H3 M3 U10 — No Details →
1.5.0 21 Apr 2024 H3 M3 U10 — No Details →
1.4.2 02 Apr 2024 H3 M3 U10 — No Details →
1.4.1 27 Mar 2024 H3 M3 U10 — No Details →
1.4.0 26 Mar 2024 H3 M3 U10 — No Details →
1.3.0 09 Mar 2024 H2 M3 U7 — Yes Details →
1.2.3 23 Feb 2024 H2 M3 U7 — Yes Details →
1.2.2 16 Feb 2024 H2 M3 U7 — Yes Details →
1.2.1 13 Feb 2024 H2 M3 U7 — Yes Details →
1.2.0 31 Jan 2024 H2 M3 U7 — Yes Details →
1.1.3 12 Jan 2024 H2 M3 U7 — Yes Details →
1.1.2 20 Dec 2023 H2 M3 U7 — Yes Details →
1.1.1 14 Nov 2023 H2 M3 U7 — Yes Details →
1.1.0 02 Nov 2023 H2 M3 U7 — Yes Details →
1.0.0 19 Oct 2023 H2 M3 U7 — Yes Details →
1.0.0-pre.18 10 Oct 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.17 09 Oct 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.16 19 Sep 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.15 09 Sep 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.14 29 Aug 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.13 15 Aug 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.12 12 Aug 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.11 11 Aug 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.10 28 Jun 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.9 16 Jun 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.8 15 Jun 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.7 14 Jun 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.6 08 Jun 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.5 02 Jun 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.4 23 May 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.3 03 May 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.2 24 Apr 2023 H2 M2 U6 — Yes Details →
1.0.0-pre.1 21 Apr 2023 H2 M2 U6 — Yes Details →
0.7.7 11 Apr 2023 H2 M2 U6 — Yes Details →
0.7.6 09 Apr 2023 H2 M2 U6 — Yes Details →
0.7.5 04 Apr 2023 H2 M2 U6 — Yes Details →
0.7.4 27 Mar 2023 H2 M2 U6 — Yes Details →
0.7.3 20 Mar 2023 H2 M2 U6 — Yes Details →
0.7.2 18 Mar 2023 H2 M2 U6 — Yes Details →
0.7.1 17 Mar 2023 H2 M2 U6 — Yes Details →
0.7.0 17 Mar 2023 H2 M2 U6 — Yes Details →
0.6.11 17 Mar 2023 H2 M2 U6 — Yes Details →
0.6.10 10 Mar 2023 H2 M2 U6 — Yes Details →
0.6.9 20 Feb 2023 H2 M2 U6 — Yes Details →
0.6.8 31 Jan 2023 H2 M2 U6 — Yes Details →
0.6.7 17 Jan 2023 H2 M2 U6 — Yes Details →
0.6.6 11 Jan 2023 H2 M2 U6 — Yes Details →
0.6.5 10 Jan 2023 H2 M2 U6 — Yes Details →
0.6.4 23 Dec 2022 H2 M2 U6 — Yes Details →
0.6.3 09 Dec 2022 H2 M2 U6 — Yes Details →
0.6.2 25 Nov 2022 H2 M2 U6 — Yes Details →
0.6.1 21 Nov 2022 H2 M2 U6 — Yes Details →
0.6.0 15 Nov 2022 H2 M2 U6 — Yes Details →
0.5.11 04 Nov 2022 H2 M2 U5 — Yes Details →
0.5.10 04 Nov 2022 H2 M2 U5 — Yes Details →
0.5.9 03 Nov 2022 H2 M2 U5 — Yes Details →
0.5.8 02 Nov 2022 H2 M2 U4 — Yes Details →
0.5.7 01 Nov 2022 H1 M2 U4 — Yes Details →
0.5.6 28 Sep 2022 H1 M2 U4 — Yes Details →
0.5.5 24 Sep 2022 H1 M2 U4 — Yes Details →
0.5.4 23 Sep 2022 H1 M2 U4 — Yes Details →
0.5.3 22 Sep 2022 H1 M2 U4 — Yes Details →
0.5.2 21 Sep 2022 H1 M2 U4 — Yes Details →
0.5.1 20 Sep 2022 H1 M2 U4 — Yes Details →
0.5.0 04 May 2022 H1 M2 U4 — Yes Details →
0.4.10 17 Apr 2022 M2 U3 — Yes Details →
0.4.9 14 Apr 2022 M2 U3 — Yes Details →
0.4.8 14 Apr 2022 M2 U3 — Yes Details →
0.4.7 05 Mar 2022 M2 U3 — Yes Details →
0.4.6 03 Mar 2022 M2 U3 — Yes Details →
0.4.5 17 Nov 2021 M2 U3 — Yes Details →
0.4.4 26 Oct 2021 M2 U3 — Yes Details →
0.4.3 12 Oct 2021 M2 U3 — Yes Details →
0.4.2 11 Oct 2021 M2 U3 — Yes Details →
0.4.1 27 Sep 2021 M2 U3 — Yes Details →
0.4.0 27 Sep 2021 M2 U3 — Yes Details →
0.3.9 25 Sep 2021 M2 U3 — Yes Details →
0.3.8 25 Sep 2021 M2 U3 — Yes Details →
0.3.7 24 Sep 2021 M2 U3 — Yes Details →
0.3.6 18 Sep 2021 M2 U3 — Yes Details →
0.3.5 15 Sep 2021 M2 U2 — Yes Details →
0.3.4 13 Sep 2021 M1 U2 — Yes Details →
0.3.3 29 Jun 2021 M1 U1 — Yes Details →
0.3.2 24 Jun 2021 M1 U1 — Yes Details →

The newest 120 of 126 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 19

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

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 bandit

Is bandit safe to use?

Vulert records 19 vulnerabilities for bandit in Hex: 0 critical, 4 high, 3 medium and 0 low, plus 12 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is bandit's Vulert package health score?

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

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

How many vulnerabilities does bandit have?

19 vulnerabilities are recorded for bandit in the Hex ecosystem: 0 critical, 4 high, 3 medium and 0 low, plus 12 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 bandit vulnerabilities disclosed?

19 vulnerabilities were recorded for bandit in the last 12 months, and the oldest entry in this database dates to 01 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 bandit 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 bandit for upcoming vulnerabilities?

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