VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.jenkins-ci.plugins:ansible: vulnerability history, versions and safety

org.jenkins-ci.plugins:ansible is a package in the Maven ecosystem. Vulert records 4 vulnerabilities for it across 16 releases, from May 2022 to May 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M4
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 org.jenkins-ci.plugins:ansible vulnerabilities

Vulert verdict on org.jenkins-ci.plugins:ansible 635.v34b_48e979c86 i

Updated on 23 Oct 2026

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

Package health score 79/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Moderate

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

  • Current release 635.v34b_48e979c86 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 16 May 2023 i
  • Highest CVSS 5.6 i
  • With no published fix 0 i
  • Stars 233 i
  • Last release 9 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by Maven Central, 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 org.jenkins-ci.plugins: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
635.v34b_48e979c86 13 Jan 2026 none MIT — Details →
588.v2a_a_a_f345e34f 11 Aug 2025 none MIT — Details →
524.v9fa_a_4c989224 18 Mar 2025 none MIT — Details →
500.v7564a_db_8feec 22 Jan 2025 none MIT — Details →
403.v8d0ca_dcb_b_502 18 Jun 2024 none MIT — Details →
0.2 13 Feb 2024 M4 Apache-2.0 Yes Details →
0.4 13 Feb 2024 M4 Apache-2.0 Yes Details →
275.v2b_cf4b_b_d239c 13 Feb 2024 none Apache-2.0 — Details →
174.vfd5323d2b_9d8 13 Feb 2024 M2 Apache-2.0 Yes Details →
148.v6b_13c6de3a_47 13 Feb 2024 M2 Apache-2.0 Yes Details →
215.v1c78933a_b_0d7 13 Feb 2024 none Apache-2.0 — Details →
0.8 13 Feb 2024 M4 Apache-2.0 Yes Details →
303.vccb_73a_956ecd 13 Feb 2024 none MIT — Details →
0.1 13 Feb 2024 M4 Apache-2.0 Yes Details →
0.6.2 13 Feb 2024 M4 Apache-2.0 Yes Details →
285.v2f044b_eb_7a_3e 13 Feb 2024 none Apache-2.0 — Details →
146.v431a_a_39d472d 13 Feb 2024 M2 Apache-2.0 Yes Details →
299.ve6759d531f0e 13 Feb 2024 none MIT — Details →
301.v29a_7f9b_0d820 13 Feb 2024 none MIT — Details →
1.1 13 Feb 2024 M2 Apache-2.0 Yes Details →
0.5 13 Feb 2024 M4 Apache-2.0 Yes Details →
235.v53d3ef91489b_ 13 Feb 2024 none Apache-2.0 — Details →
276.vef26df37652f 13 Feb 2024 none Apache-2.0 — Details →
1.0 13 Feb 2024 M3 Apache-2.0 Yes Details →
231.va_d0cb_802c621 13 Feb 2024 none Apache-2.0 — Details →
253.v4fe719ffdd8a_ 13 Feb 2024 none Apache-2.0 — Details →
307.va_1f3ef06575a_ 13 Feb 2024 none MIT — Details →
204.v8191fd551eb_f 13 Feb 2024 M2 Apache-2.0 Yes Details →
0.3 13 Feb 2024 M4 Apache-2.0 Yes Details →
0.3.1 13 Feb 2024 M4 Apache-2.0 Yes Details →
205.v4cb_c48657c21 13 Feb 2024 M2 Apache-2.0 Yes Details →
217.v1696cee03265 13 Feb 2024 none Apache-2.0 — Details →
240.vc26740a_625c0 13 Feb 2024 none Apache-2.0 — Details →
0.6.1 13 Feb 2024 M4 Apache-2.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2023 2

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

03 Vulnerabilities

Recorded vulnerabilities for org.jenkins-ci.plugins:ansible

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-1000149: Jenkins Ansible Plugin man in the middle vulnerability 5.6 medium 1.0 13 May 2022
CVE-2020-2310: Missing permission checks in Jenkins Ansible Plugin allow enumerating credentials IDs 4.3 medium 1.1 24 May 2022
CVE-2023-32982: Jenkins Ansible Plugin stores and displays secrets in plain text 4.3 medium 205.v4cb 16 May 2023
CVE-2023-32983: Jenkins Ansible Plugin job configuration form does not mask variables 4.3 medium 205.v4cb 16 May 2023

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 org.jenkins-ci.plugins:ansible

Is org.jenkins-ci.plugins:ansible safe to use?

Vulert records 4 vulnerabilities for org.jenkins-ci.plugins:ansible in Maven: 0 critical, 0 high, 4 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is org.jenkins-ci.plugins:ansible's Vulert package health score?

Vulert scores org.jenkins-ci.plugins:ansible 79/100, which reads as in good shape. 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 org.jenkins-ci.plugins:ansible affected?

No. 635.v34b_48e979c86, 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 org.jenkins-ci.plugins:ansible should I use?

635.v34b_48e979c86 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 org.jenkins-ci.plugins:ansible have?

4 vulnerabilities are recorded for org.jenkins-ci.plugins:ansible in the Maven ecosystem: 0 critical, 0 high, 4 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.jenkins-ci.plugins:ansible vulnerabilities disclosed?

0 vulnerabilities were recorded for org.jenkins-ci.plugins:ansible in the last 12 months, and the oldest entry in this database dates to 13 May 2022. 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 org.jenkins-ci.plugins: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 org.jenkins-ci.plugins:ansible for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.jenkins-ci.plugins: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.