VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

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

org.jenkins-ci.plugins:active-directory is a package in the Maven ecosystem. Vulert records 12 vulnerabilities for it across 78 releases, from Jan 2022 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
12 vulnerabilities recorded C3 H2 M6 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 24 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.jenkins-ci.plugins:active-directory vulnerabilities

Vulert verdict on org.jenkins-ci.plugins:active-directory 2.971.v653d8b_6e5548 i

Updated on 23 Oct 2026

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

Package health score 67/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Moderate

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

  • Current release 2.971.v653d8b_6e5548 — unaffected i
  • Vulnerabilities on record 12 over 4 years · 3 in the last year i
  • Latest disclosure 24 Jun 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Stars 53 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, 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 org.jenkins-ci.plugins:active-directory, 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.971.v653d8b_6e5548 30 Sep 2026 none non-standard — Details →
2.967.vf4e254546a_b_3 29 Jul 2026 none non-standard — Details →
2.958.vc03fe0b_a_8e65 21 Jul 2026 none non-standard — Details →
2.41.2 12 Jun 2026 none non-standard — Details →
2.41.1 20 May 2026 L1 non-standard Yes Details →
2.41 23 Oct 2025 M2 L1 non-standard Yes Details →
2.40 29 Apr 2025 M2 L1 non-standard Yes Details →
2.39 07 Feb 2025 M2 L1 non-standard Yes Details →
2.38 18 Nov 2024 M2 L1 non-standard Yes Details →
2.37 03 Oct 2024 M2 L1 non-standard Yes Details →
2.36 01 Aug 2024 M2 L1 non-standard Yes Details →
2.35 14 Feb 2024 M2 L1 non-standard Yes Details →
1.21 13 Feb 2024 H2 M6 L1 — Yes Details →
2.23 13 Feb 2024 M4 L1 non-standard Yes Details →
2.27 13 Feb 2024 M3 L1 non-standard Yes Details →
2.34 13 Feb 2024 M2 L1 non-standard Yes Details →
1.47 13 Feb 2024 H2 M6 L1 non-standard Yes Details →
2.2 13 Feb 2024 H2 M6 L1 non-standard Yes Details →
2.10 13 Feb 2024 H1 M6 L1 non-standard Yes Details →
1.43 13 Feb 2024 H2 M6 L1 non-standard Yes Details →
1.29 13 Feb 2024 H2 M6 L1 — Yes Details →
1.48 13 Feb 2024 H2 M6 L1 non-standard Yes Details →
2.9 13 Feb 2024 H1 M6 L1 non-standard Yes Details →
2.0 13 Feb 2024 H2 M6 L1 non-standard Yes Details →
1.44 13 Feb 2024 H2 M6 L1 non-standard Yes Details →
2.13 13 Feb 2024 M6 L1 non-standard Yes Details →
2.3 13 Feb 2024 H1 M6 L1 non-standard Yes Details →
1.35 13 Feb 2024 H2 M6 L1 — Yes Details →
2.17 13 Feb 2024 C3 M6 L1 non-standard Yes Details →
2.4 13 Feb 2024 H1 M6 L1 non-standard Yes Details →
2.8 13 Feb 2024 H1 M6 L1 non-standard Yes Details →
2.22 13 Feb 2024 M4 L1 non-standard Yes Details →
2.31 13 Feb 2024 M2 L1 non-standard Yes Details →
1.39 13 Feb 2024 H2 M6 L1 non-standard Yes Details →
2.32 13 Feb 2024 M2 L1 non-standard Yes Details →
2.25.1 13 Feb 2024 M3 L1 non-standard Yes Details →
1.31 13 Feb 2024 H2 M6 L1 — Yes Details →
1.34 13 Feb 2024 H2 M6 L1 — Yes Details →
2.25 13 Feb 2024 M4 L1 non-standard Yes Details →
2.16 13 Feb 2024 M6 L1 non-standard Yes Details →
2.33 13 Feb 2024 M2 L1 non-standard Yes Details →
1.22 13 Feb 2024 H2 M6 L1 — Yes Details →
1.37 13 Feb 2024 H2 M6 L1 — Yes Details →
1.38 13 Feb 2024 H2 M6 L1 — Yes Details →
1.49 13 Feb 2024 H2 M6 L1 non-standard Yes Details →
2.20 13 Feb 2024 M4 L1 non-standard Yes Details →
2.15 13 Feb 2024 M6 L1 non-standard Yes Details →
1.27 13 Feb 2024 H2 M6 L1 — Yes Details →
2.16.1 13 Feb 2024 M6 L1 non-standard Yes Details →
1.30 13 Feb 2024 H2 M6 L1 — Yes Details →
1.42 13 Feb 2024 H2 M6 L1 non-standard Yes Details →
2.28 13 Feb 2024 M3 L1 non-standard Yes Details →
1.18 13 Feb 2024 H2 M6 L1 — Yes Details →
1.41 13 Feb 2024 H2 M6 L1 non-standard Yes Details →
2.6 13 Feb 2024 H1 M6 L1 non-standard Yes Details →
2.19 13 Feb 2024 C3 M6 L1 non-standard Yes Details →
2.29 13 Feb 2024 M3 L1 non-standard Yes Details →
2.1 13 Feb 2024 H2 M6 L1 non-standard Yes Details →
2.30.1 13 Feb 2024 M2 L1 non-standard Yes Details →
1.46 13 Feb 2024 H2 M6 L1 non-standard Yes Details →
2.24.1 13 Feb 2024 M4 L1 non-standard Yes Details →
1.24 13 Feb 2024 H2 M6 L1 — Yes Details →
1.45 13 Feb 2024 H2 M6 L1 non-standard Yes Details →
2.18 13 Feb 2024 C3 M6 L1 non-standard Yes Details →
2.24 13 Feb 2024 M4 L1 non-standard Yes Details →
1.28 13 Feb 2024 H2 M6 L1 — Yes Details →
2.30 13 Feb 2024 M3 L1 non-standard Yes Details →
1.19 13 Feb 2024 H2 M6 L1 — Yes Details →
2.12 13 Feb 2024 M6 L1 non-standard Yes Details →
1.36 13 Feb 2024 H2 M6 L1 — Yes Details →
1.25 13 Feb 2024 H2 M6 L1 — Yes Details →
1.32 13 Feb 2024 H2 M6 L1 — Yes Details →
2.5 13 Feb 2024 H1 M6 L1 non-standard Yes Details →
2.7 13 Feb 2024 H1 M6 L1 non-standard Yes Details →
1.23 13 Feb 2024 H2 M6 L1 — Yes Details →
1.26 13 Feb 2024 H2 M6 L1 — Yes Details →
1.33 13 Feb 2024 H2 M6 L1 — Yes Details →
2.11 13 Feb 2024 M6 L1 non-standard Yes Details →
2.26 13 Feb 2024 M3 L1 non-standard Yes Details →
2.23.1 13 Feb 2024 M4 L1 non-standard Yes Details →
1.20 13 Feb 2024 H2 M6 L1 — Yes Details →
2.14 13 Feb 2024 M6 L1 non-standard Yes Details →

All 82 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 8
  • 2023 1
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for org.jenkins-ci.plugins:active-directory

The 5 most severe of 12 vulnerabilities recorded for this package

Search all 12 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-2299: Improper Authentication in Jenkins Active Directory Plugin 9.8 critical 2.20 24 May 2022
CVE-2020-2300: Improper Authentication in Jenkins Active Directory Plugin 9.8 critical 2.20 24 May 2022
CVE-2020-2301: Authentication cache in Active Directory Jenkins Plugin allows logging in with any password 9.8 critical 2.20 24 May 2022
Jenkins Active Directory Plugin - Certificate Verification Bypass 8.1 high 2.3 13 May 2022
Jenkins Active Directory Plugin Improper certificate validation with StartTLS 7.4 high 2.11 13 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 org.jenkins-ci.plugins:active-directory

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

Vulert records 12 vulnerabilities for org.jenkins-ci.plugins:active-directory in Maven: 3 critical, 2 high, 6 medium and 1 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:active-directory's Vulert package health score?

Vulert scores org.jenkins-ci.plugins:active-directory 67/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).

Is the latest version of org.jenkins-ci.plugins:active-directory affected?

No. 2.971.v653d8b_6e5548, 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:active-directory should I use?

2.971.v653d8b_6e5548 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:active-directory have?

12 vulnerabilities are recorded for org.jenkins-ci.plugins:active-directory in the Maven ecosystem: 3 critical, 2 high, 6 medium and 1 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:active-directory vulnerabilities disclosed?

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

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