VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

ansible: vulnerability history, versions and safety

ansible is a package in the PyPI ecosystem. Vulert records 142 vulnerabilities for it across 120 releases, from Sep 2013 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
142 vulnerabilities recorded C9 H24 M27 L6 U76
i
5 with no fix published

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

See the unfixed vulnerabilities →
i
6 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 ansible vulnerabilities

Vulert verdict on ansible 14.5.0 i

Updated on 23 Oct 2026

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

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • 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 14.5.0 — affected i
  • Vulnerabilities on record 142 over 12 years · 6 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 5 i
  • Depended on by 199 packages i
  • Stars 142 i
  • Last release this month i
  • Licence GPL-3.0-or-later i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 ansible, 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
15.0.0a3 14 Oct 2026 M1 L1 U6 GPL-3.0-or-later No Details →
14.5.0 06 Oct 2026 M1 L1 U6 GPL-3.0-or-later No Details →
15.0.0a2 29 Sep 2026 M1 L1 U6 GPL-3.0-or-later No Details →
15.0.0a1 22 Sep 2026 M1 L1 U6 GPL-3.0-or-later No Details →
14.4.0 08 Sep 2026 M1 L1 U6 GPL-3.0-or-later No Details →
14.3.1 14 Aug 2026 M1 L1 U6 GPL-3.0-or-later No Details →
14.3.0 11 Aug 2026 M1 L1 U6 GPL-3.0-or-later No Details →
14.2.0 14 Jul 2026 M1 L1 U6 GPL-3.0-or-later No Details →
13.8.0 18 Jun 2026 M1 L1 U6 GPL-3.0-or-later No Details →
14.1.0 18 Jun 2026 M1 L1 U6 GPL-3.0-or-later No Details →
14.0.0 02 Jun 2026 M1 L1 U6 GPL-3.0-or-later No Details →
14.0.0rc1 26 May 2026 M1 L1 U6 GPL-3.0-or-later No Details →
14.0.0b1 22 May 2026 M1 L1 U6 GPL-3.0-or-later No Details →
13.7.0 19 May 2026 M1 L1 U6 GPL-3.0-or-later No Details →
14.0.0a4 29 Apr 2026 M1 L1 U6 GPL-3.0-or-later No Details →
14.0.0a3 21 Apr 2026 M1 L1 U6 GPL-3.0-or-later No Details →
13.6.0 21 Apr 2026 M1 L1 U6 GPL-3.0-or-later No Details →
14.0.0a2 14 Apr 2026 M1 L1 U6 GPL-3.0-or-later No Details →
14.0.0a1 07 Apr 2026 M1 L1 U6 GPL-3.0-or-later No Details →
13.5.0 25 Mar 2026 M1 L1 U6 GPL-3.0-or-later No Details →
13.4.0 24 Feb 2026 M1 L1 U6 GPL-3.0-or-later No Details →
13.3.0 29 Jan 2026 M1 L1 U6 GPL-3.0-or-later No Details →
13.2.0 30 Dec 2025 M1 L1 U6 GPL-3.0-or-later No Details →
12.3.0 09 Dec 2025 M1 L1 U6 GPL-3.0-or-later No Details →
11.13.0 09 Dec 2025 U1 GPL-3.0-or-later Yes Details →
13.1.0 09 Dec 2025 M1 L1 U6 GPL-3.0-or-later No Details →
13.0.0 19 Nov 2025 M1 L1 U6 GPL-3.0-or-later No Details →
13.0.0rc1 11 Nov 2025 M1 L1 U6 GPL-3.0-or-later No Details →
11.12.0 05 Nov 2025 M1 U1 GPL-3.0-or-later Yes Details →
13.0.0b1 05 Nov 2025 M1 L1 U6 GPL-3.0-or-later No Details →
12.2.0 05 Nov 2025 M1 L1 U6 GPL-3.0-or-later No Details →
13.0.0a5 29 Oct 2025 M1 L1 U6 GPL-3.0-or-later No Details →
13.0.0a4 21 Oct 2025 M1 L1 U6 GPL-3.0-or-later No Details →
13.0.0a3 15 Oct 2025 M1 L1 U6 GPL-3.0-or-later No Details →
13.0.0a2 07 Oct 2025 M1 L1 U6 GPL-3.0-or-later No Details →
11.11.0 07 Oct 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.1.0 07 Oct 2025 U1 GPL-3.0-or-later Yes Details →
13.0.0a1 24 Sep 2025 M1 L1 U6 GPL-3.0-or-later No Details →
11.10.0 09 Sep 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.0.0 09 Sep 2025 U1 GPL-3.0-or-later Yes Details →
12.0.0rc1 02 Sep 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.0.0b5 26 Aug 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.0.0b4 21 Aug 2025 M1 U1 GPL-3.0-or-later Yes Details →
11.9.0 12 Aug 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.0.0b3 05 Aug 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.0.0b2 29 Jul 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.0.0b1 22 Jul 2025 M1 U1 GPL-3.0-or-later Yes Details →
11.8.0 16 Jul 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.0.0a9 09 Jul 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.0.0a8 01 Jul 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.0.0a7 25 Jun 2025 M1 U1 GPL-3.0-or-later Yes Details →
11.7.0 17 Jun 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.0.0a6 12 Jun 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.0.0a5 04 Jun 2025 M1 U1 GPL-3.0-or-later Yes Details →
11.6.0 20 May 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.0.0a4 12 May 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.0.0a3 06 May 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.0.0a2 24 Apr 2025 M1 U1 GPL-3.0-or-later Yes Details →
11.5.0 22 Apr 2025 M1 U1 GPL-3.0-or-later Yes Details →
12.0.0a1 16 Apr 2025 M1 U1 GPL-3.0-or-later Yes Details →
11.4.0 25 Mar 2025 M1 U1 GPL-3.0-or-later Yes Details →
11.3.0 25 Feb 2025 M1 U1 GPL-3.0-or-later Yes Details →
11.2.0 28 Jan 2025 M1 U1 GPL-3.0-or-later Yes Details →
9.13.0 03 Dec 2024 M1 U2 GPL-3.0-or-later No Details →
10.7.0 03 Dec 2024 M1 U2 GPL-3.0-or-later No Details →
11.1.0 03 Dec 2024 M1 U2 GPL-3.0-or-later No Details →
11.0.0 19 Nov 2024 M1 U2 GPL-3.0-or-later No Details →
11.0.0rc1 13 Nov 2024 M1 U2 GPL-3.0-or-later No Details →
11.0.0b2 06 Nov 2024 M1 U2 GPL-3.0-or-later No Details →
11.0.0b1 05 Nov 2024 M1 U2 GPL-3.0-or-later No Details →
10.6.0 05 Nov 2024 M1 U2 GPL-3.0-or-later No Details →
9.12.0 05 Nov 2024 M1 U2 GPL-3.0-or-later No Details →
11.0.0a2 15 Oct 2024 M1 U2 GPL-3.0-or-later No Details →
9.11.0 08 Oct 2024 M1 U2 GPL-3.0-or-later No Details →
10.5.0 08 Oct 2024 M1 U2 GPL-3.0-or-later No Details →
11.0.0a1 25 Sep 2024 M1 U2 GPL-3.0-or-later No Details →
9.10.0 10 Sep 2024 M1 U2 GPL-3.0-or-later No Details →
10.4.0 10 Sep 2024 M1 U2 GPL-3.0-or-later No Details →
10.3.0 13 Aug 2024 M1 U2 GPL-3.0-or-later No Details →
9.9.0 13 Aug 2024 M1 U2 GPL-3.0-or-later No Details →
9.8.0 16 Jul 2024 M1 U2 GPL-3.0-or-later No Details →
10.2.0 16 Jul 2024 M1 U2 GPL-3.0-or-later No Details →
9.7.0 18 Jun 2024 M1 U2 GPL-3.0-or-later No Details →
10.1.0 18 Jun 2024 M1 U2 GPL-3.0-or-later No Details →
10.0.1 06 Jun 2024 M1 U2 GPL-3.0-or-later No Details →
9.6.1 06 Jun 2024 M1 U2 GPL-3.0-or-later No Details →
10.0.0rc1 28 May 2024 M1 U2 GPL-3.0-or-later No Details →
10.0.0b1 21 May 2024 M1 U2 GPL-3.0-or-later No Details →
10.0.0a3 14 May 2024 M1 U2 GPL-3.0-or-later No Details →
10.0.0a2 30 Apr 2024 M1 U2 GPL-3.0-or-later No Details →
9.5.1 24 Apr 2024 M1 U2 GPL-3.0-or-later No Details →
10.0.0a1 09 Apr 2024 M1 U2 GPL-3.0-or-later No Details →
9.4.0 27 Mar 2024 M1 U2 GPL-3.0-or-later No Details →
9.3.0 27 Feb 2024 M1 U2 GPL-3.0-or-later No Details →
9.2.0 30 Jan 2024 M1 U2 GPL-3.0-or-later No Details →
8.7.0 06 Dec 2023 M1 U2 non-standard No Details →
9.1.0 05 Dec 2023 M1 U2 GPL-3.0-or-later No Details →
9.0.1 21 Nov 2023 M1 U2 GPL-3.0-or-later No Details →
9.0.0rc1 14 Nov 2023 M1 U2 GPL-3.0-or-later No Details →
8.6.1 09 Nov 2023 M1 U2 non-standard No Details →
8.6.0 07 Nov 2023 M1 U2 — No Details →
9.0.0b1 07 Nov 2023 M1 U2 — No Details →
9.0.0a3 17 Oct 2023 M1 U2 — No Details →
8.5.0 11 Oct 2023 M1 U2 — No Details →
9.0.0a2 05 Oct 2023 M1 U2 — No Details →
9.0.0a1 28 Sep 2023 M1 U2 — No Details →
8.4.0 12 Sep 2023 M2 U3 — No Details →
8.3.0 15 Aug 2023 M2 U3 — No Details →
8.2.0 18 Jul 2023 M2 U3 — No Details →
8.1.0 22 Jun 2023 M2 U4 — No Details →
7.7.0 22 Jun 2023 M2 U4 — No Details →
8.0.0 30 May 2023 M2 U4 — No Details →
8.0.0rc1 23 May 2023 M2 U4 — No Details →
7.6.0 23 May 2023 M2 U4 — No Details →
8.0.0b1 16 May 2023 M2 U4 — No Details →
8.0.0a3 02 May 2023 M2 U4 — No Details →
8.0.0a2 26 Apr 2023 M2 U4 — No Details →
7.5.0 26 Apr 2023 M2 U4 — No Details →
8.0.0a1 12 Apr 2023 M2 U4 — No Details →
7.4.0 28 Mar 2023 M2 U4 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2013 2
  • 2015 1
  • 2016 1
  • 2017 3
  • 2018 21
  • 2019 14
  • 2020 33
  • 2021 26
  • 2022 34
  • 2023 1
  • 2025 2
  • 2026 4

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

03 Vulnerabilities

Recorded vulnerabilities for ansible

The 5 most severe of 142 vulnerabilities recorded for this package

Search all 142 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2017-7550: Ansible Insertion of Sensitive Information into Log File Vulnerability 9.8 critical 2.4.1.0 13 May 2022
CVE-2017-7481: Ansible - Unsafe Lookup-Plugin Results 9.8 critical 2.3.1.0 06 Sep 2018
CVE-2014-4966: Ansible Arbitrary Code Execution 9.8 critical 1.6.7 17 May 2022
CVE-2014-4678: Ansible Code Injection Vulnerability 9.8 critical 1.6.4 24 May 2022
CVE-2014-4967: Ansible Arbitrary Code Execution 9.8 critical 1.6.7 17 May 2022

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 ansible

Is ansible safe to use?

Vulert records 142 vulnerabilities for ansible in PyPI: 9 critical, 24 high, 27 medium and 6 low, plus 76 not yet rated. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is ansible's Vulert package health score?

Vulert scores ansible 50/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 ansible affected?

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

Which version of ansible should I use?

14.5.0 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 ansible have?

142 vulnerabilities are recorded for ansible in the PyPI ecosystem: 9 critical, 24 high, 27 medium and 6 low, plus 76 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 ansible vulnerabilities disclosed?

6 vulnerabilities were recorded for ansible in the last 12 months, and the oldest entry in this database dates to 16 Sep 2013. 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 ansible 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 ansible for upcoming vulnerabilities?

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